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

Discloses return fields (decision, verdict, score, reasoning, SLA/health) and performance (<100ms). No annotations exist, so no contradiction; description provides adequate behavioral context.

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?

Three sentences, each valuable. First defines purpose, second what it returns, third usage. Front-loaded and no 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?

With one required parameter and no output schema, the description covers purpose, output structure, performance, and usage guideline. Complete for a simple check tool.

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 has 0% description coverage. Description implies 'address' is the counterparty's wallet/agent/token, but does not explicitly define format or constraints. Partial compensation.

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 the tool as 'THE pre-payment trust check' for verifying counterparties before paying USDC over x402. It uniquely identifies its role among siblings, none of which overlap.

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?

Explicitly instructs to call before settling USDC and to refuse on BLOCK verdict. Does not mention when not to use or alternatives, but context is sufficient for decision.

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