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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world reach are covered. The description adds one genuinely useful behavioral detail — the listing score is present only 'if listed', i.e. a conditionally-present field — but says nothing about data freshness, caching, or what happens for an unknown ticker.

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?

One sentence, front-loaded with the core value (price and 24h change) before the colon expands into the ARC AI-specific extras. Dense but every clause names a distinct returned dataset; no filler.

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?

An output schema exists, so return-value explanation is not strictly required, yet the description usefully previews the payload shape. For a one-parameter read tool the coverage is nearly sufficient; the missing piece is guidance on selecting this over the more specialized sibling tools.

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%: the single ticker parameter is documented with format examples (SOL, JUP, BONK). The description adds no format, casing, or resolution rules beyond what the schema already states, 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 names the resource (a coin) and enumerates exactly what data is returned — price, 24h change, whale buys/sells, latest per-agent call with graded accuracy, and listing score. It is a clear retrieval purpose, but it never distinguishes itself from siblings like get_whale_flows or get_track_record, some of whose data it aggregates.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, even though sibling tools (get_whale_flows, get_track_record, get_signals, analyze_token) clearly overlap with the data this tool returns. The agent must infer that this is the 'overview' entry point versus the specialized siblings.

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