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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds real behavioral context beyond them: the record is 'frozen and never edited', and it covers a fixed 24-hour horizon, so the agent knows the data is an immutable historical snapshot rather than a live read.

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 resource and the check_coin routing are front-loaded, but the opening is a long run-on with slash-separated jargon ('against / careful / clear (or launch facts only)') that is hard to parse and spends words on stylistic flavor rather than agent-relevant information.

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 burden of describing the return contents, and it does so reasonably: verdict, tallied findings, rationale, dev/funder's other coins, and 24h outcome. It is dense but covers what an agent needs to know before calling.

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% and there is a single required 'address' parameter whose pattern is fully documented in the schema. The description adds no parameter-specific meaning, so the baseline 3 applies.

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 identifies a distinct resource: the frozen launch-day call record (verdict, findings, dev/funder coins, 24h outcome) for a Robinhood Chain token. It explicitly distinguishes itself from the sibling check_coin ('Not the coin now: use check_coin for that'), though the 'Toll made... against / careful / clear' jargon muddies the exact nature of the resource.

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?

It names the alternative and the condition that selects it ('Not the coin now: use check_coin for that') and states a hard scope restriction ('Robinhood Chain only'). It lacks an explicit positive when-to-use trigger, but the implied context (wanting the historical launch call) is legible from the resource description.

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