binary_diff

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the notable behavior that both the input scope and the output are 'bounded,' implying result truncation, but it never explains the truncation rule, error cases (missing/unreadable file), or performance characteristics on large intervals.

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?

A single front-loaded sentence with no filler, efficiently pairing the operation with its result. It is terse to the point of under-specifying, but nothing in it is wasted.

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?

No output schema and no annotations beyond the safety hints, so the description must explain return shape, bounding/truncation semantics, and parameter behavior — none of which it does. For a 5-parameter file-comparison tool this leaves the agent guessing.

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 description coverage is 0% across 5 parameters, so the description carries the burden. 'Bounded intervals' weakly alludes to offset/length and 'bounded difference ranges' hints at max_ranges, but path_a/path_b, offset=0, length=null, and the max_ranges=100 default/truncation behavior are all left unexplained.

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+resource ('Compare bounded disk-file intervals') and names the return artifact ('bounded difference ranges'), which clearly separates it from siblings like binary_read, binary_inspect, and binary_patch_preview. It does not explicitly name a sibling, so it stops short of a 5.

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?

No statement of when to use this versus binary_patch_preview/binary_patch_apply or binary_inspect, no prerequisites (e.g. whether the two files must be the same size), and no exclusions. The agent must infer the use case from the name alone.

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