delimit_diff

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

States 'Side effects: read-only' and mentions the backend call. Since no annotations exist, the description carries full burden. It is clear and honest, but could add more detail on error handling.

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?

Well-structured with sections: purpose, usage guidelines, sibling contrast, side effects. Every sentence adds value and is front-loaded. No wasted 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?

With only two simple parameters, complete schema coverage, and an output schema, the description fully covers the tool's behavior, usage boundaries, and side effects. Nothing missing.

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% and both parameters are already described in the input schema. The description does not add additional semantics beyond what the schema provides, so baseline 3 is appropriate.

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 'Diff two OpenAPI specs and list all changes (pure diff, no policy).' It uses a specific verb and resource, and distinguishes from siblings like delimit_lint and delimit_diff_report.

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?

Explicit 'When to use' and 'When NOT to use' sections with alternative tools (delimit_lint for CI gate, delimit_diff_report for HTML report). Also provides sibling contrast.

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