Read Multiple Files

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

Adds key behavioral traits beyond annotations: 'Failed reads for individual files won't stop the entire operation' and 'Only works within allowed directories'. Annotations only provide readOnlyHint, so description significantly enhances understanding.

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?

Four sentences covering action, efficiency benefit, failure behavior, and directory constraint. No redundant information, and the most critical details come first.

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?

Despite having an output schema (not shown), the description provides essential operational context: multiple file handling, partial failures, and access limitations. With simple parameters and annotations, it adequately prepares the agent.

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 already has 100% coverage with a clear description of the 'paths' parameter. Tool description does not add new semantic meaning beyond reinforcing the allowed directories constraint, meeting baseline expectations.

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?

Description clearly states 'Read the contents of multiple files simultaneously', specifying the action and resource. It distinguishes from siblings like 'read_file' by emphasizing batch operation and efficiency for multiple files.

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 says 'more efficient than reading files one by one when you need to analyze or compare multiple files', guiding when to use. However, it does not directly name alternative tools like 'read_file' for single files, though siblings are listed for context.

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