Standard Tools: birdeyeTradeData

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds the list of supported chains and the Hedera exclusion. No additional behavioral details like output format or rate limits are provided, but the annotations cover safety.

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 purpose, and the second lists supported chains and an exclusion. No unnecessary words.

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?

The description is sufficient for selecting the tool but lacks details about the output format or what 'detailed trade data' includes. Given no output schema, a brief note on return structure would enhance completeness.

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%, so the description does not add much beyond the schema. It redundantly lists chains and mentions Hedera exclusion, which is already in the chain parameter's description. The address parameter is not further elaborated.

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 explicitly states 'Get detailed trade data for a specific token from Birdeye' and lists supported chains. It also distinguishes itself from the sibling hederaTokensSwapQuote by noting that Hedera is not supported and provides the alternative tool.

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 clearly indicates when to use (for trade data on supported chains) and when not to use (for Hedera, use hederaTokensSwapQuote). However, it could be more explicit about differentiating from other trade-related siblings like solanaGetTokenPairPrice.

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