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

The annotations only declare it is non-read-only, idempotent, non-destructive and open-world; the description adds the material facts an agent needs: it is a paid tool at $0.25 in USDC on Base or Arbitrum One, the call must POST JSON to the paid_url with an x402 v2 PAYMENT-SIGNATURE header, and dry_run is intercepted before the payment gate so it is free. These payment, cost, and auth details go well beyond the annotation set. No contradiction with idempotentHint=true or destructiveHint=false.

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?

Purpose and the free-preview option are front-loaded, and every remaining sentence carries invocation-critical information (payment header, price, paid URL). The colon-chained phrasing is choppy and the bare token 'paid_url' requires the agent to connect it to the trailing 'Paid URL' string, but there is little outright waste.

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?

This is a high-complexity tool with nested parameters, a payment gate, and an output schema, and the description covers the payment model, the free escape hatch, and the sibling alternative. Return values need not be explained because an output schema exists. The only gap is the lack of explicit guidance on how policy strings or context affect the verdict.

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?

With 100% schema description coverage, the schema already documents every parameter, including the detailed idempotency_key contract. The description only reinforces dry_run=true as the free-quote mode; it adds no meaning about intent, policy, subject, or context beyond structured fields. Baseline 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?

The opening clause names the specific job: a pre-payment trust check producing a signed verdict on 'who is paid, what's delivered, what changed' against supplied policies. It is telegraphic rather than a clean verb+resource sentence, but an agent can tell it produces a verdict about a spend target. It also distinguishes itself from one sibling by naming trust_report as the endpoint-verdict alternative, though it leaves trust_assurance unaddressed.

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?

'Before paying' states the triggering condition clearly, and 'Free quote: dry_run=true' tells the agent how to preview without cost. 'Endpoint verdict: trust_report' routes to a sibling for a different use case. There is no explicit when-not-to-use clause or prerequisite list, which keeps it from a 5.

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