Standard Tools: birdeyeTradeData

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

Annotations already declare readOnlyHint:true, destructiveHint:false, idempotentHint:true, and openWorldHint:true. The description adds value by specifying which chains are supported and which are not, providing additional behavioral context beyond the annotations. No contradiction exists.

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 two sentences: the first states the core purpose, and the second lists supported chains with a critical exclusion and alternative. No unnecessary words or repetition.

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 simple read-only tool with 2 parameters (100% schema coverage), clear annotations, and no output schema, the description adequately covers purpose, chain support, and exclusion. No additional information is needed for an agent to correctly select and invoke the 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 description coverage is 100% (both 'chain' and 'address' are described). The description adds extra context by listing supported chains explicitly and noting the Hedera exclusion with an alternative, which supplements the schema's enum and default value.

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 states the tool retrieves 'detailed trade data for a specific token from Birdeye' and lists all supported chains, explicitly distinguishing from the sibling tool for Hedera by saying 'NOT supported: Hedera (use hederaTokensSwapQuote instead)'. This provides a specific verb+resource and differentiates from alternatives.

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 explicitly lists supported chains and provides an alternative tool for the unsupported Hedera chain, giving clear guidance on when to use this tool and when to use a sibling instead.

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