Read Multiple Files

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

Annotations provide readOnlyHint and openWorldHint, which are consistent. The description adds value by noting that 'Failed reads for individual files won't stop the entire operation', which is a key behavioral trait not captured by annotations. This helps the agent understand partial failure behavior.

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?

The description is four sentences, front-loaded with the core purpose. It avoids redundancy and each sentence offers useful information. Slightly longer than minimal but justified by the additional behavioral details.

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?

Given the tool handles multiple files with partial failures, the description covers efficiency, batch operation, failure handling, and directory restriction. With an output schema present, return format is documented. It provides sufficient context for an agent to use the tool correctly.

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 100%, so baseline is 3. The description reinforces that each path must be a string within allowed directories, but adds no new meaning beyond the schema's description. It does hint at the output format (content with path reference), but that's more about return values than parameter semantics.

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 starts with 'Read the contents of multiple files simultaneously', clearly stating the verb and resource. It distinguishes from sibling tools like 'read_file' by highlighting batch efficiency and the ability to handle multiple files at once.

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 says this tool is 'more efficient than reading files one by one', providing a clear use case. It also mentions that failed reads won't stop the operation and that it only works within allowed directories, offering practical guidance. However, it could explicitly state when not to use it.

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