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

No annotations provided, so description carries full burden. It discloses that tool fetches realtime data across multiple sources (price, whale flow, liquidity, matches). Could be more explicit about read-only nature and rate limits, but sufficiently transparent for a data retrieval tool.

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?

Two concise sentences with clear purpose, usage guidance, and examples. No unnecessary words; every sentence adds value.

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?

No output schema exists, so description must explain return data. It lists realtime price, CEX whale flow, on-chain liquidity with slippage, and upcoming matches. Could mention format or caveats, but it's fairly complete for a realtime data tool.

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 100% with one parameter 'token' already described as symbol. Description adds examples (ASR, BAR, CHZ) but schema already mentions them. Does not add significant meaning beyond schema, so baseline 3 is appropriate.

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?

Description clearly states it is a 'SINGLE-TOKEN deep dive' listing specific data points (realtime price, CEX whale flow, liquidity with slippage, upcoming matches) and explicitly distinguishes from sibling tokenintel_briefing (market-wide overview).

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?

Explicitly says 'default tool to call before evaluating a trading decision on a specific token' and provides when to use ('when you have a target token in mind') and when not (use tokenintel_briefing for market-wide overview).

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