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

The description discloses that the tool may initially return a 402 challenge, requiring the caller to 'sign and retry with PAYMENT-SIGNATURE' – a behavioral trait not fully captured by annotations. It also notes the two possible returns (402 challenge or fulfillment JSON). Annotations already indicate non-readOnly, so the description adds context about the protocol flow, though it doesn't mention financial side effects explicitly.

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 two sentences, front-loaded with the core action and output, followed by a compact workflow. Every sentence adds essential information without redundancy or filler.

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?

The description sufficiently explains the x402 flow, including prerequisites and retry behavior, for a complex tool with 11 parameters and an output schema. It doesn't elaborate on parameter specifics (rightly left to the schema) or the manifest fields, but the core operational context is present. Slightly more coverage on what 'one-time product' implies could earn a 5.

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% with detailed parameter descriptions, so the description adds little parameter-level meaning. The only tie is referencing PAYMENT-SIGNATURE, which the schema already explains in the paymentSignature parameter. No additional parameter semantics are provided; this is a baseline 3.

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's function: 'Purchase a one-time product via x402 (returns 402 challenge or fulfillment JSON)'. This specifies a verb (purchase), a resource (one-time product), and the mechanism (x402). It distinguishes itself from sibling tools like get_x402_manifest or list_products by explicitly being the purchase action.

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?

The description gives explicit usage prerequisites: 'Call get_x402_manifest first, verify method/path/network/amount/payTo, then sign and retry with PAYMENT-SIGNATURE.' It clearly indicates the workflow and when this tool is appropriate (after the manifest is obtained). It does not explicitly mention when not to use it or alternatives, so it misses the top tier.

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