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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the cost ($0.20 Base USDC) and implies the input is ABI snapshots, but it does not explain the report format, expected ABI structure, failure modes, or whether any external calls or side effects occur.

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 short and front-loaded: the first sentence defines what the tool produces, and the second sentence adds cost information. No sentence is wasted, though the brevity leaves important invocation details out.

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?

Given the opaque input schema, lack of output schema, absence of annotations, and many sibling tools, this description is not complete enough for an agent to invoke the tool correctly. The agent knows a report about API changes is produced and that it costs money, but not how to supply the snapshots or what the response will look like.

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 input schema is an opaque object with additionalProperties allowed and 0% description coverage, so the description must compensate. It only says 'supplied ABI snapshots' at a high level and does not explain how the snapshots should be structured, how many are needed, or which fields denote the old versus new ABI. This is minimal meaningful semantical guidance.

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 deliverable ('Contract ABI change report') and its source data ('supplied ABI snapshots'), which makes the tool's function reasonably clear and distinct from generic change-report siblings. However, it lacks an explicit action verb like 'compare' or 'generate', so the exact operation is somewhat inferred.

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?

There is no guidance on when to use this tool versus alternatives such as json_change_report, openapi_difference_report, or code_diff_summary. The only extra directive is the cost, which is not a usage condition or selection criterion.

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