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

With no annotations, the description carries the full behavioral burden, and it delivers unusual value: it discloses determinism ('no LLM'), the exact cost and payment rail ('$0.10 per call, paid with USDC over x402'), and it clarifies which output dominates ('the verdict is the gate's; the rest is context beside it'). Read-only safety is only implied, not stated.

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?

A single dense sentence, but it is front-loaded with the purpose and then ordered by component. Every clause (gate, wallet scan, trending, payment terms) adds distinct information, with little waste.

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 annotations and no output schema, the description must convey both behavior and return shape, and it does: it names the three returned signals, states what the verdict means, and covers cost and payment. Only read-only/non-destructive guarantees and any latency or rate-limit details are absent.

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 already 100%, so the baseline is 3, but the description adds real meaning: it explains that 'wallet' is optional and conditionally triggers the wallet-scan component, which the schema alone does not convey. The token parameter's role in the verdict is also clarified.

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 concrete verb and scope ('Everything to check before one swap on Base, in one call') and enumerates the three bundled signals: the rule-based trade gate, the wallet spam/honeypot scan, and trending-pool membership. An agent can distinguish this composite precheck from siblings trade_gate, wallet_check, and token_check without opening any 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?

It gives clear contextual guidance for the optional wallet scan ('when a wallet is given') and frames this as the single-call aggregate of checks that would otherwise require several tools. It stops short of explicitly stating when to prefer this over calling trade_gate or wallet_check alone, so it earns a 4 rather than a 5.

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