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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful, non-structured context: the $0.10 USDC cost, that x402 or prepaid credits are accepted, and that it is excluded from the free trial. It omits latency/caching behavior, which is the remaining gap.

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?

The purpose is front-loaded and every clause carries signal, but the long parenthetical inventory of outputs is dense and runs mid-sentence. Slightly heavy for the amount of routing information an agent needs before the schema fills in the rest.

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 an output schema present, the description needn't explain returns, and it still names the headline signals. Combined with the payment/price disclosure, an agent has enough to select and invoke it correctly; only the choice versus trade-precheck-cached and caching/latency behavior are undeclared.

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 100% with 4 params, so the schema already documents address, chain, side and amountUsd. The description only alludes to amountUsd ('for your trade size') and to per-chain fees; it adds no format, default or constraint detail beyond the schema. Baseline 3 applies.

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 ('Deep pre-trade check') and explicitly positions it as a superset of the sibling /trade/precheck, enumerating the extra signals (whale/exchange flows, news buzz, Polymarket odds, AI risk officer). An agent can distinguish it from trade-precheck and trade-precheck-cached without opening a 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?

Implies when to use it (when the base precheck isn't enough — you need flows, news, odds, AI call) and states a clear gating condition: paid only, not in the free trial, $0.10 per call. It does not name trade-precheck-cached as the cheaper alternative, so routing between the three precheck variants is left partly to inference.

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