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

Beyond the annotations (idempotentHint/destructiveHint), the description explains the idempotency contract in detail: same request_id+amount retries never pay twice if a durable response or payment attempt already exists. It also discloses the 402 challenge behavior for a missing proof and the header-only constraint, which are critical behavioral traits not present in the schema.

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?

Dense but well-organized description; each sentence adds a distinct piece of information (purpose, amount, idempotency, header, errors, alternatives). The later sentences about the full catalog and front_door are helpful context but slightly tangential, preventing a perfect score.

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?

For a payment tool with no output schema, the description covers the core input rules, error behavior, and idempotency, but does not explicitly describe the shape/content of a successful response or how the durable response should be read. It points to the /api/tools catalog and front_door for orientation, and the annotations mitigate uncertainty, so it remains mostly complete.

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% and both parameter descriptions already explain the semantics. The description adds the cross-parameter rule that retry requires the exact same request_id and amount together, which is a behavioral constraint beyond the individual schema entries. It also reaffirms the whole-dollar conversion and no-rounding detail.

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?

Description explicitly states 'Purchase prepaid city fee credit through x402 only' – a specific verb, resource, and delivery mechanism. It also distinguishes from web-only PayPal routes, making the tool's scope clear relative to purchase-related siblings like credit_gift and credit_preflight.

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?

Provides explicit when-to-use guidance: use x402 only, send proof in the outer X-PAYMENT header rather than tool arguments, and retry with the same request_id and amount after a timeout. It explicitly tells the agent when not to pay again and notes that PayPal routes and the human window are web-only, naming front_door as an orienting alternative.

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