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

Annotations mark it read-only and non-destructive, and the description adds genuinely useful behavioral context beyond them: the prepaid-credit model, the exact cost (0.0005 USDT per 100 rows), and a fallback per-request payment path with its own price. Return format, row limits relative to `limit`, and cursor expiry are left unstated.

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?

Compact and front-loaded: what it is, then pricing, then payment paths. The embedded URL and price figures are dense but each earns its place for an agent that must decide whether it can afford to call the tool.

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 tool with an empty schema description, a nested `filters` object, and no output schema, the description spends its budget on monetization and says nothing about what rows come back, how cursor paging terminates, or what filter keys exist. The gaps fall exactly where the structured fields provide no help.

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 coverage is 0% for five parameters (from, to, limit, cursor, filters), and the description supplies no per-parameter meaning. 'Filtered and paginated' only faintly gestures at `filters`/`cursor`; the direction semantics of from/to and the accepted filter keys are entirely undocumented.

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+resource: 'Premium bulk cross-chain transfer history, filtered and paginated.' This is clearly distinguishable from free siblings like get_address_crosschain or get_crosschain_stats through the 'premium bulk export' framing.

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?

Gives explicit routing: use orbitpay_info for payment/signing steps, or pay per request via x402 on the HTTP route for wallet-holding agents. It does not, however, tell the agent when to prefer this over the free cross-chain siblings.

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