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

Annotations already establish readOnly and non-destructive, so the description's job is to add the commercial and procedural context, which it does: prepaid credit at 0.0005 USDT per 100 rows, an explicit prerequisite step (orbitpay_info) before invocation, and a concrete alternative payment path with price, chain, and URL. It stops short of stating rate limits, credit-exhaustion behavior, or result-size behavior beyond the limit cap.

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?

Purpose and pricing lead, followed by the payment procedure and the alternative route — a sensible front-loaded order with little filler. The URL and price detail are dense but each earns its place for a paid 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?

With no output schema, no parameter descriptions, and a nested open-ended filters object, an agent still cannot construct a correct call from this description — filter key vocabulary, cursor semantics, and returned row shape are all undefined. Payment is covered thoroughly; the actual invocation surface is not.

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 five parameters, including a nested free-form 'filters' object with additionalProperties string, so the description carries the full burden. It only gestures at 'filtered and paginated', which hints at from/to and cursor but explains nothing about filter key syntax, cursor lifetime, or the interaction between limit and cursor.

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 verb and resource ('bulk cross-chain transfer history') plus its two defining traits, filtered and paginated. The word 'bulk' implicitly separates it from the per-address sibling get_address_crosschain, but no sibling is named, so the differentiation is inferential rather than explicit.

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?

It gives real operational routing guidance — call orbitpay_info for payment/signing, or use the x402 HTTP route instead if the agent holds a wallet — which tells the agent how to pay. It says nothing, however, about when this premium export should be chosen over the free cross-chain siblings such as get_address_crosschain or get_crosschain_stats.

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