read_multiple_files_content

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a read operation (implied by 'Read'), describes error handling ('Failed reads for individual files won't stop the entire operation'), and mentions the return format ('Each file's content is returned with its path as a reference'). However, it doesn't specify permission requirements or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with zero waste - first states purpose, second provides usage guidance, third discloses error behavior. Each sentence earns its place by adding distinct value. The description is appropriately sized and front-loaded with the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read operation with no annotations and no output schema, the description provides good coverage of purpose, usage context, and error behavior. However, it doesn't specify the exact return format structure or whether there are any limitations on the number/size of files that can be read simultaneously.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents the single 'paths' parameter. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Read') and resource ('contents of multiple files'), specifies the source ('workspace filesystem'), and distinguishes it from the sibling 'read_file_content' by emphasizing simultaneous reading of multiple files. It provides specific purpose beyond just the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool ('more efficient than reading files one by one when you need to analyze or compare multiple files') and provides a clear alternative ('reading files one by one'). It also mentions the sibling tool 'read_file_content' implicitly through this comparison.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.