birdeye-top-traders

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions the source (BirdEye) and the time frame (today's data), but does not describe return format, ranking criteria, limits, or any side effects. For a read operation, it lacks context about what the response will look like.

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 a single concise sentence that front-loads the main action and resource. No superfluous wording.

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 adequate for a zero-parameter tool, but it does not specify what constitutes 'top traders' (e.g., by volume, profit) or the return structure. Since there is no output schema, the description could provide more detail about the expected response.

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 tool has zero parameters, so there is no parameter semantic burden. The baseline of 4 applies as the description appropriately requires no parameter explanations.

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 uses a specific verb 'Get' and identifies the resource 'top traders on Solana from BirdEye', which clearly distinguishes it from siblings like 'birdeye-trending-tokens'. The parenthetical 'showing today's data' adds temporal specificity.

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 usage for retrieving top trader data, but it does not explicitly state when to use this tool over alternatives such as 'birdeye-trending-tokens' or 'token-lookup'. No when-to-use or when-not-to-use guidance is provided beyond the basic function.

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