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

Annotations only supply readOnlyHint and openWorldHint, so the description carries the rest and does so well: it discloses the verdict taxonomy (high/caution/low), the shape of the payload (reasons tagged by section plus a one-line summary per section), the chain restriction, and the commercial/access model — 5¢ per call from prepaid credits, 3 free premium calls per day, and the required Authorization: Bearer <key> header. Pricing and auth requirements are precisely the operational facts an agent cannot infer from annotations or schema.

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 statement is front-loaded and the scope, alternatives, and access terms follow in a logical order with no filler sentences; every clause carries information. It is a dense single paragraph, though, and the pricing/auth sentence could be one clause shorter without losing meaning.

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 describing the return artifact — a single verdict with per-section tagged reasons and per-section one-line summaries. Combined with the covered sub-checks, chain restriction and auth/payment terms, an agent has everything needed to decide to call it and to interpret the result.

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?

With a single parameter at 100% schema description coverage, the schema already defines "token" as a 0x contract address on Robinhood Chain, so the baseline is high. The description reinforces the domain by repeatedly scoping everything to Robinhood Chain tokens, but it adds no syntax, format or validation nuance beyond the schema.

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 opens with a specific verb and resource ("full check on a Robinhood Chain token in one call") and enumerates the exact sections covered: safety (sellability, taxes, owner), price and pool depth, holder concentration and linked holders, launch bundling, and dev history. It then states the concrete return artifact — one verdict (high, caution, low) with tagged reasons — which no sibling name implies. This is clearly distinguishable from token_holders, bundle_check and dev_check, which each cover only one of those sections.

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?

Explicit routing is given on both sides: "Use this first for 'is this token safe?', 'should I worry about this token?', 'check this token'" establishes the entry point, and "Use token_holders, bundle_check or dev_check for more detail on one part" names the alternatives and the condition that selects them. The scope limit "Robinhood Chain only for now" further constrains when the tool applies.

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