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

With no annotations, the description carries the behavioral burden and does useful work: it discloses the free preview / paid full report model, the exact per-call price, the payment rail (USDC on Base via x402), and the HTTP endpoint. It does not cover rate limits, error behavior, or response shape, but the pricing and payment mechanics are unusually transparent.

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 description is dense but front-loaded: report scope comes first, followed by pricing/payment and endpoint information. Every clause conveys operational detail, with no filler.

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 data-retrieval tool with no output schema and no annotations, the description does well by enumerating what the report includes and how payment works. It stops short of describing the response structure or failure modes, which keeps it from being fully complete.

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 coverage is 50%, so the description has to add value. It names the supported chains and, importantly, documents the x402 payment field in params._meta, which is not represented in the input schema but is required for invocation. It does not expand on the address format beyond what the schema already says.

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 specific verb and resource: a token due-diligence report covering price, liquidity, security, supply checks, and a risk verdict for tokens on four named chains. It is clearly distinguishable from generic chain-read tools, though it does not explicitly contrast with the sibling token_dd__batch.

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?

The description makes the use case apparent: due diligence on a token contract. It also notes a free preview and a $0.01 full report, but does not explicitly say when to use this versus token_dd__batch or other token-related siblings, nor does it state exclusions.

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