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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely useful behavior beyond them: the premium paywalled nature, archival data source, filtered and paginated delivery, and per-row pricing. The 'export' wording aligns with read-only semantics, so there is no contradiction.

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?

Three sentences, each carrying distinct information: purpose, cost/payment routing, and the alternative HTTP route, with the purpose front-loaded. The URL template 'https://orbitwan.io/idx<route>' is cryptic and would benefit from a concrete route value, but overall there is no wasted prose.

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 payment and signing flow is covered thoroughly, which is critical and unusual context for this tool, but the rest of the picture is incomplete. With no output schema and 0% parameter documentation, the description omits the export's return format and the semantics of `to`/`from`/`filters`, leaving an agent unable to fully validate its request.

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 description coverage is 0% across 5 parameters, so the description must compensate, but it only gestures via 'filtered and paginated', loosely mapping to filters/cursor/limit. The meanings of `to` and `from` (addresses, chains, or time bounds?) and the valid keys for the `filters` object are unexplained, so an agent cannot reliably build a correct request.

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 first sentence, 'Premium bulk cross-chain transfer history from ARCHIVE, filtered and paginated', states a specific resource (cross-chain transfer history from archive) and operation (bulk export), and it matches the title. Scope markers like 'bulk' and 'ARCHIVE' distinguish it from siblings such as get_crosschain_stats and orbitpay_tags_export, though no sibling is named explicitly.

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 provides concrete usage conditions: prepaid credit at a stated rate, an explicit directive that 'Payment and signing steps: call orbitpay_info', and an alternative x402 HTTP route for wallet-holding agents with its own cost. It lacks explicit when-not-to-use guidance or exclusions against sibling history/stats tools.

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