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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it specifies the returned metrics, shows the tool is address-driven, and indicates multichain support. It does not mention data freshness or rate-limit behavior, but it does not contradict the annotations.

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 description is compact: one purpose sentence, one return-value sentence, and one example. The example earns its place by showing the exact call shape with real addresses. The slight inconsistency between 'price, liquidity, volume' in the first clause and 'market cap, 24h price change, holder count' in the second prevents a perfect score.

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?

For a straightforward read-only tool with three well-documented parameters and no output schema, the description is largely sufficient: it names the primary returned fields, gives a valid example, and indicates chain support. It could be more complete by aligning the promised output fields and mentioning what happens for unsupported chains or invalid addresses, but those are minor gaps.

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?

The input schema already has 100% parameter coverage with clear descriptions for chain, _apiKey, and address, so the baseline is 3. The description adds an explicit executable example and a placeholder API key, which is helpful but largely redundant with the schema examples. It does not materially deepen parameter meaning beyond what the schema provides.

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 clearly identifies the resource ('token overview') and says it 'Returns market cap, 24h price change, and holder count for a Solana (or multichain) token by contract address.' This is a specific verb+resource with enough detail to distinguish it from sibling tools like birdeye_token_holders and birdeye_token_trades. It is not a 5 because it does not explicitly contrast itself with those siblings, and the opening phrase 'price, liquidity, volume' does not exactly match the listed returned fields.

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?

The description implies this tool is for a current, single-token market snapshot by listing overview metrics and showing an example call. However, it never states when to prefer this over birdeye_token_holders, birdeye_token_trades, or birdeye_gainers_losers, nor does it give any exclusions. The usage context is clear enough by implication, but not explicit.

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