Standard Tools: searchEvmTokensBirdeye

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

Annotations already indicate read-only, idempotent behavior. The description adds that it supports multiple chains, but lacks details on rate limits, pagination, or result format. With annotations covering safety, the description adds some but limited behavioral context.

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 action, and includes essential context. No wasted words. Every part earns its place.

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 two-parameter search tool, the description is adequate but lacks information about return format (e.g., what fields are returned, pagination). With no output schema, the burden is higher, and the description falls short.

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 baseline is 3. The description does not add extra meaning beyond schema; for example, it doesn't explain that chainId 1=ethereum, 56=bsc, etc., which would be helpful.

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 it searches for EVM tokens on Birdeye, with a specific verb ('Search') and resource ('evm tokens on Birdeye'). It also lists supported chains, distinguishing it from sibling tools like birdeyeTrendingTokens or searchCryptoByName.

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?

Usage context is implied: use for EVM token searches on Birdeye. However, no explicit guidance on when not to use it or what alternatives exist, such as birdeyeTrendingTokens for trending tokens.

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