read_multiple_files empty array

Describe the bug
The read_multiple_files function lacks clear documentation about its parameter structure and behavior, causing AI assistants to use it incorrectly without explicit instruction.
To Reproduce
Steps to reproduce the behavior:

Ask AI to use read_multiple_files function without providing parameter format instruction
AI attempts to use function with incorrect parameter structure
Function call fails or behaves unexpectedly
Only works when explicitly told: "read_multiple_files takes 'paths' parameter as string array with full file paths, returns content for each file with path as separator"

Expected behavior
The function should have clear documentation stating that it requires a "paths" parameter as a string array containing full file paths, does not accept empty arrays, and returns file content with path separation.
Logs
Function calls fail when AI uses incorrect parameter structure without explicit instruction about the required format.
Additional context
This documentation gap affects AI assistant usability and requires manual instruction for proper function usage. The parameter structure should be self-documenting or clearly specified in the function schema.

Start by locating the read_multiple_files function and its tool schema. Update the parameter documentation to describe paths as a string array of full file paths, state that empty arrays are unsupported, and explain the path-separated results. Done means the schema clearly communicates the accepted structure and behavior without extra instruction.