read_multiple_files

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

Beyond the readOnlyHint annotation, the description reveals that 'Individual failures don't stop the batch — partial results are returned,' and that encoding is 'auto-detected per file.' These behavioral details help an agent anticipate outcomes.

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 efficiently cover purpose, usage guidance, and parameter semantics. No redundant information, and the key action is front-loaded.

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?

The description covers concurrency, encoding support, and partial failure behavior, which are the main operational concerns. With an output schema present, no return-format details are needed. It is well-rounded for a batch-read tool.

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?

With 0% schema description coverage, the description fully compensates by explaining 'paths (required array)' and 'encoding (optional, auto-detected per file),' adding semantic meaning beyond the raw schema.

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 it 'Read multiple files concurrently with encoding support,' which specifies both the verb and the resource, and distinguishes it from sibling tools like read_text_file by emphasizing the multi-file and non-UTF-8 use case.

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?

The description explicitly advises to 'PREFER THIS when reading several non-UTF-8 files at once,' providing a concrete when-to-use scenario. It does not name sibling alternatives directly, but the context makes the guidance clear enough.

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