diff_diff_files

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

The description discloses the return format and error condition on unreadable files. No annotations exist, so the description provides necessary behavioral context, though it could mention size limitations or side effects.

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 succinct sentences with front-loaded purpose and clear output structure. No unnecessary words.

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?

Covers main functionality, output, and error case. Missing documentation for the context parameter, but otherwise sufficient for a simple file comparison 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?

The description implies path_a and path_b are file paths, but does not explain the optional 'context' parameter. With 0% schema coverage, the description partially compensates but leaves a gap for context.

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 compares two files and returns a unified diff with specific output fields. The tag '[diff]' and return structure distinguish it from sibling tools like diff_diff_text or diff_diff_stats.

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 implies file-based comparison vs text-based, but does not explicitly state when to choose this tool over alternatives like diff_diff_text or diff_diff_similar.

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