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

With no annotations, the description carries the full burden and does disclose the key non-obvious traits: cost ($0.01/call in USDC), network (eip155:8453), the exact payment injection point (params._meta["x402/payment"]), a free /sample, and the HTTP method/URL. It stops short of describing the response shape or whether failures still incur 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?

It is a single dense paragraph, but two of its sentences pitch /report and /sample rather than this tool, and pricing/payment boilerplate is repeated ("$0.01" appears three times). Useful content is present but not front-loaded on the actual operation.

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 1-param, no-annotation, no-output-schema tool, the description covers payment and cost well but leaves the return value, token format, and chain scope of the tokens unspecified. An agent knows how to pay but not precisely what to send or expect back.

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 0% and the single `tokens` property is an undescribed string. The description adds the meaningful constraint that up to 10 tokens are accepted per call, but it never states the encoding (comma-separated? addresses vs symbols?) or what happens beyond 10, so the agent can still easily call it incorrectly.

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?

"Base token due diligence over x402" plus "/price now takes up to 10 tokens per $0.01 call for bulk screening" hints that this endpoint returns token price data for a batch of up to 10 tokens. However, the first two sentences describe /report and /sample rather than this tool, so the agent must parse past sibling-endpoint marketing to infer what basedue__price actually returns.

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 contrast between /report (bundled DD + reference price + exit cost, one token) and /price (bulk, up to 10 tokens) implicitly tells the agent when to pick this tool for bulk screening. There is no explicit when-not guidance and no statement of prerequisites beyond the payment requirement.

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