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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context beyond those annotations: it is quote-first, must not infer amounts, must not pay before a payment_intent, and must never request a private key. This gives the agent actionable rules beyond the structured hints.

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 exceptionally concise: two short sentences with no wasted words. It front-loads the core purpose and immediately follows with the most important safety constraints. Every clause earns its place.

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 read-only explanatory tool with no parameters, the description supplies the essential context: the flow is quote-first, on Solana Mainnet, uses USDC, and carries strict safety rules. It does not enumerate the full lifecycle or explain how payment_intent is obtained, but given the tool's educational role and rich annotations, the definition is largely 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?

The tool has zero parameters and the schema description fully covers what the tool returns ('Return the exact quote-first paid-service lifecycle and safety rules'). With no parameters, the description does not need to explain parameter semantics, so the baseline of 4 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 description clearly states a specific verb and resource: 'Explain the quote-first Solana Mainnet USDC payment flow.' It also includes concrete guardrails ('Never infer an amount, never pay before a payment_intent, and never request a private key') that distinguish this informational tool from execution-oriented siblings like submit_payment or create_paid_job.

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 implies the tool is for explaining the payment flow, and the safety rules strongly suggest when not to perform actions, but it does not explicitly state when to use this guide versus alternatives. It lacks direct exclusion statements such as 'use submit_payment to actually pay' or 'use create_paid_job to request a quote.'

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