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

Goes well beyond the read-only/idempotent/open-world annotations by disclosing pricing ($0.15/call over x402 on Base), the auth path (prepaid x-credit-token header for unlimited calls, no free tier, no API key required), the no-charge failure mode, and the 2%-impact cap on max size. These are exactly the operational traits annotations cannot convey.

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?

Front-loads the composition and verdict model before pricing/auth details, and every sentence carries distinct information (composition, verdict rule, returns, failure mode, cost, headers). The clauses are dense and run long, but there is no obvious filler to cut.

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 complex composite tool, it covers verdict semantics, per-check visibility, the unverified list, the receipt, the no-GO/no-charge path, and the full payment/auth model. With an output schema present, return values needn't be spelled out, and nothing an agent needs to invoke it correctly is missing.

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%, so the schema already documents both address and amountUsd; the description only restates 'Required input: address.' It adds a faint hint about amountUsd's role in the exit-liquidity/max-size read but no format or syntax detail, so 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 action (runs five named pre-trade checks in parallel on a Base token) and the bundled resources it wraps (pre-trade-gate, b20-gate, owner-powers, dump-risk, clanker-token-audit). It explicitly differentiates itself from those siblings by positioning them as sub-components rather than alternatives, so an agent can identify it as the aggregator 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?

Clearly states the operational rule: 'GO only if every applicable check ran clean; if a gating check could not run there is no GO and no charge,' and notes b20-gate is N/A for non-B20 tokens. It gives strong context but never explicitly tells the agent when to call this bundle versus the individual sibling tools (pre_trade_gate, b20_gate, etc.).

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