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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered structurally. The description adds useful behavioral context beyond that: it states the outputs produced (real-transfer net, prefunded net, break-even premium) and the units for fee inputs. It does not say whether the trade path is modeled as a single round-trip or whether 'prefunded' assumes capital already parked on B, which is a meaningful modeling assumption.

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?

Two compact sentences, front-loaded with the trade sequence before the computed outputs, with zero filler. The density borders on cryptic ('usdt_back', 'break-even premium') but nothing needs trimming.

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?

No output schema exists, and with 8 parameters at 0% schema coverage the description would need to carry more weight than it does. It names the three result figures it returns, which is genuinely helpful, but leaves the semantics of the amount, trips, and usdt_back inputs undefined for a calculation whose correctness depends on them.

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 8 parameters and there is no enum. The description only clarifies units for two of them (fees in percent, withdrawal fee in coins); 'trips', 'amount', and especially 'usdt_back' remain completely unexplained, and 'buy'/'sell' as price inputs is only implied by 'at prices you give'.

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 concrete multi-step operation: buy on exchange A, withdraw, sell on exchange B, and compute real-transfer/prefunded net plus break-even premium. That is a specific verb+resource and clearly separates it from sibling calculators like manual_calculator or execution_cost. It stops short of naming an alternative outright, but the purpose is unambiguous.

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?

There is no explicit when-to-use guidance and no mention of the many sibling tools that overlap in domain (transfer_routes, execution_cost, manual_calculator, venue_execution_cost). The agent must infer that this is the pricing-input arbitrage calculator rather than route discovery or cost aggregation.

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