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

With no annotations, the description steps up well: it discloses the paid-call model, the price ($0.01 USDC), the settlement chain (Base, eip155:8453), the x402 mechanism and the exact payment parameter (params._meta["x402/payment"]), plus the underlying HTTP endpoint. It does not cover rate limits, whether the free preview differs in fields, or what happens on insufficient payment.

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 capability and price lead, followed by the payment mechanics and endpoint. It is dense and mostly front-loaded, though the mixing of marketing ('Free preview') with payment plumbing in one sentence slightly muddies the scan.

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 no annotations, so the description must carry the full burden. It does describe the report's contents well, but leaves the batch-vs-single ambiguity unresolved and gives no sense of result shape, error behavior, or how the preview differs from the paid report.

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 50%: `chain` is constrained by an enum and `address` is documented as a 0x-prefixed contract address, so the schema carries most of the load. The description adds nothing about parameter semantics and notably fails to clarify how a tool named 'batch' relates to the single chain/address input.

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 ('Token due-diligence report for any Base/ETH/BSC/Arbitrum token') and enumerates the report contents (price/liquidity, honeypot, mint authority, tax, holder concentration, supply checks, verdict). This clearly separates it from generic chain-read or price siblings. However, the 'batch' in the name is never explained, and the schema accepts a single chain+address, leaving the agent unsure what 'batch' means relative to token_dd__check.

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?

Usage context is implied rather than explicit: 'Free preview; full report $0.01' tells the agent there are tiers and a cost, but it never says when to pick this over token_dd__check or basedue__report. There are no stated exclusions or prerequisites beyond the payment detail.

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