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

Annotations already cover read-only and open-world nature, and the description adds context they cannot carry: the scope limitation (no recall status open/closed), the data source (as published by NHTSA), and a full cost model ($0.002 USDC per successful call via x402 on Base/Solana/Arc, failed calls not charged). Cost and billing behavior on failure are exactly the traits an agent needs before invoking a paid tool.

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?

Front-loaded with the core purpose, then exclusions, then alternatives, then pricing — a sensible priority order. The final pricing sentence is dense (three chains, four payment rails) but each clause carries decision-relevant information, so little 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?

With an output schema present, the description need not explain return values, and it still summarizes them. For a simple three-parameter lookup it covers scope, exclusions, sibling routing, and payment, leaving nothing an agent needs in order to call it correctly.

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 100%, and the schema already supplies examples ("honda", "accord") and the year range 1950-2100. The description only restates the make/model/year triple without adding format, normalization, or partial-match guidance, so the baseline of 3 applies.

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 and resource ("US NHTSA safety recalls") scoped to make, model and model year, and enumerates the returned fields (campaign number, component, summary, report date, remedy flags). It also explicitly names what it is not (no VIN lookup, no open/closed status), so an agent can distinguish it from the decoder and complaints siblings without opening a schema.

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?

Names both relevant alternatives and the exact condition that selects each: travel_nhtsa_vehicle_complaints "when you need US NHTSA owner-filed vehicle complaints" and travel_nhtsa_vpic_vehicle_decoder "when you need to decode a VIN". It also states the exclusion ("Recalls only; no VIN lookup"), giving explicit when-to-use and when-not-to-use guidance.

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