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

Annotations already cover read-only, non-destructive and open-world behavior, yet the description adds substantial context beyond them: an asynchronous queue for never-before-read coins, a returned wait time before retry, a free-tier quota of 10 new coins per day with already-read coins free, and the caveat that results are "never a verdict." The queueing also explains the otherwise puzzling idempotentHint=false, though the description does not say what happens when the quota is exhausted.

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 purpose is front-loaded in the opening clause, but the body is one long run-on sentence with stacked parentheticals (app page, API, MCP server, x402 payments, Chrome extension, Telegram bot, public code) that is hard to parse on a single read. The rate-limit and quota details earn their place, but the delivery could be split into shorter, scannable statements.

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?

With no output schema, the description carries the return contract and does so well: the label set (product found / partly found / not found / not read), per-claim verdicts with the supporting line, and which components answered. Combined with queueing and quota behavior, an agent has enough to call and interpret it; only edge cases like quota exhaustion or unreadable sites remain unspecified.

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%, with both parameters documented in the schema (chain defaulting to rh, token requiring a 0x contract address), so the baseline of 3 applies. The description contributes no additional parameter meaning such as accepted identifier forms or chain values beyond what the schema already states.

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: it reads a coin's site, launch post and README, then checks each stated claim against the chain and against live components. The framing question ("is there a real product behind a coin on Robinhood Chain?") makes the intent unmistakable, but it never names or contrasts with a sibling such as check_coin, so an agent must infer the boundary.

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 is implied rather than stated: it is for a coin on Robinhood Chain whose product claims you want verified, and the polling instruction ("the answer says how many seconds to wait before calling again") is genuinely actionable. However, there is no explicit when-to-use versus check_coin or check_tx, and no stated conditions where this tool is the wrong choice.

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