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

The annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds substantial behavior context: pricing tiers, wallet credit requirements, EIP-191 signing details, x402 alternative, and the fallback behavior of returning the manual instead of data. This goes well beyond the structured annotations.

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 front-loaded with purpose and every sentence conveys unique information, but the text is long and dense. Technical specifics like EIP-191, x402, and header names could be condensed without losing meaning.

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-parameter, read-only info tool with no output schema, the description covers the return content, pricing model, payment authentication paths, and fallback behavior. Minor ambiguity remains about whether the info call itself is charged, but overall the description is sufficiently 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?

With zero parameters, schema description coverage is 100%, so the baseline is 4. The description adds relevant contextual information about required HTTP headers (X-Payer, X-Timestamp, X-Signature) for payment, even though these are not schema parameters.

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 that the tool returns the live payment manual for OrbitWan premium data, providing a specific verb (returns) and resource (payment manual). This distinguishes it from sibling data retrieval tools like get_token or get_transaction, which return data rather than payment instructions.

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 explains when the manual is returned (unauthenticated or with no wallet credit) and details both OrbitPay and x402 payment methods. However, it does not explicitly route the agent to an alternative tool; it only describes an alternative protocol, so the when-to-use guidance is strong but not fully explicit.

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