read_multiple_files

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: partial failures do not abort the batch. It stops short of stating whether failures are reported per-file, what the result shape is, how missing files surface, or whether encoding applies uniformly.

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?

Two short sentences with zero waste; the core capability leads and the failure-handling caveat follows. Nothing is padded or restated from the schema.

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?

There is no output schema, so the description should explain how per-file results and errors are returned for a batch read — that is the main thing an agent needs and it is absent. The failure-tolerance statement partially covers the behavioral gap, but the return contract remains undocumented.

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 coverage is only 50%: 'paths' is documented in-schema as an array of absolute paths, but 'encoding' has no schema description and the tool description adds nothing about it. The description mentions no parameters at all, so it does not compensate for the uncovered half.

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?

States a specific verb and resource ('Read multiple files') plus the batch scope ('in a single call'), which is enough to separate it from the singular read_file sibling. It does not name that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Batch usage is implied by 'multiple files in a single call', and the failure-tolerance note hints at the batching rationale. However, there is no explicit guidance on when to prefer this over repeated read_file calls, nor any precondition such as path absoluteness being required.

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