diff_ast_trees

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

With no annotations, the description carries the behavioral burden. It usefully discloses that whitespace and cosmetic comment edits are ignored and that a Base L2 micropayment applies, but it does not mention the output format, input payload shape, language support, or any limitations of the AST diffing process.

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 a single compact sentence with the core behavior front-loaded. The parenthetical cost note is short, relevant, and actionable given the paymentSignature parameter. There is no filler or redundancy.

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?

The tool is moderately complex—AST diffing with two revisions—but the description does not explain how to structure the payload, what the response looks like, or how this tool relates to close siblings. An agent would struggle to invoke it correctly without additional external documentation.

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%, which earns the baseline score, but the payload parameter is only described generically as 'Input parameters or JSON string payload for the tool execution.' The description adds no concrete detail about how to encode the two code revisions into the payload.

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 states a specific verb ('Computes'), a clear resource ('semantic Abstract Syntax Tree differences between two code revisions'), and a distinguishing behavior ('ignoring whitespace and cosmetic comment edits'). This makes it easy to differentiate from generic diff tools like diff_json_deep or git_diff_semantic_summarizer.

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 when to use the tool—when semantic AST-level differences matter and cosmetic changes should be ignored—but it never explicitly says when to prefer this over sibling tools or when not to use it. No alternatives are named.

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