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

With no annotations, the description carries the full burden and does well: it discloses the voting model, veto behavior, the returned artifacts, and the per-call price. It omits whether any state is written, latency, and rate-limit behavior, which matters for a paid paid-per-call endpoint.

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 sentences plus a price line, front-loaded with the differentiating mechanism before the commercial detail. Nothing is padded and the agent roster is the useful kind of specificity.

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?

There is no output schema, and the description compensates by naming the return fields (verdict, tally, evidence). It leaves the verdict vocabulary and confidence scale unspecified, which is the main remaining gap for an agent that must interpret the response.

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%, including the full x402 first-call/402/pay/retry flow for paymentProof, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond implying a token is required.

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 mechanism — seven named rule-based agents voting with confidence and reasons, with Guardian/Wash Detector veto power — and the output (consensus verdict, tally, evidence). That is far more concrete than a generic 'analyze token'. It never names a sibling (e.g. token_audit or wash_trading_check) to contrast against, so it stops short of the 5 bar.

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?

No statement of when to choose this over siblings such as token_audit, wash_trading_check, or hype_signal, and no prerequisites (supported chains are only in the schema). The cost note ('0.02 USDC per call') hints at a paid path but is not usage guidance.

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