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

Annotations only declare a safe read, but the description adds substantial behavior: it is free, it idempotently returns a manual, it details the exact signing scheme (EIP-191 personal_sign over 'orbitwan-api <unix_seconds>'), the required X-Payer/X-Timestamp/X-Signature headers, and a per-request x402 fallback. This is far beyond what annotations provide.

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?

Front-loads the key point ('Free.') and stays on topic, but the x402 parenthetical with wire-version details is dense and could be trimmed. Every sentence is relevant to a payment manual, so little is wasted.

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?

With no params, no output schema, and safe-read annotations, the description fully covers what the tool returns and why. It explains both the OrbitPay prepaid-credit flow and the x402 alternative, so an agent knows how to proceed after calling.

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 there is no parameter semantics to miss; baseline 4 applies. The description correctly signals a no-argument, informational call.

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?

States a specific verb and resource ('Returns the live payment manual') and enumerates exactly which four sibling tools it documents. An agent can distinguish this from the premium data tools without opening any schema.

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?

Explains the trigger (called unauthenticated or with no wallet credit, the four tools return this manual) and offers an alternative path (x402 clients pay without OrbitPay onboarding). It does not explicitly order the agent to call this first, but the context for use is clear.

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