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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: accepted payment rails (x402 USDC on Base, PRIVI token), the $0.001 payout wallet figure, and the billing rule that failed calls are never charged — a detail that materially affects how an agent retries paid calls.

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?

A single compact sentence that front-loads the core question ('which tools are paid, their price per call') before payment mechanics. The trailing '$0.001' attached to 'payout wallet' is slightly ambiguous (is it the payout amount or a minimum?), costing a point.

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 zero-argument informational tool with an output schema already present, the description covers the substantive gaps: what pricing data exists, how payment works, and the failure-charging policy. It does not say whether the price list is static or dynamically priced, which would be the last useful detail.

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 takes zero parameters, so the baseline of 4 applies; there is no parameter meaning for the description to compensate for.

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 states a specific resource (pricing for paid tools: per-call price, payment rails, payout wallet) rather than restating the name. It is clearly separable from siblings like quantum_status or quantum_backends, though the verb is implicit (a noun-phrase list rather than 'returns pricing for...').

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?

Usage is only implied: an agent infers it should call this before invoking paid tools to learn cost and payment method. There is no explicit when-to-use, no when-not-to-use, and no named alternative among the many quantum_* siblings.

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