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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful context about the data source ('Ottoscan analytics') and the specific metrics returned, which goes beyond annotations, though it does not disclose details like pagination or exact response format. This is adequate but not rich.

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 with no fluff, and the key subject is front-loaded. However, the line break and parenthetical are slightly awkward, and it could be more structured, but overall it is tight and readable.

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 one-parameter tool, the description lists the output metrics but fails to explain the 'days' parameter's effect and does not distinguish from the sibling 'chain_deployments'. With no output schema, the description leaves gaps about what exactly the tool returns and how to parameterize it, making it incomplete for safe invocation.

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 0% and the only parameter 'days' is not explained in the description at all. The description mentions 'daily' stats but does not clarify that the 'days' parameter controls the time range, leaving the agent without essential semantic information for this parameter.

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 states it provides 'Robinhood Chain deployment statistics' and enumerates specific metrics (daily deploy/token counts, top deployers, total contract/verified counts), giving a clear idea of what it does. However, it lacks a verb and does not explicitly differentiate from the sibling 'chain_deployments', making it less sharp than a fully explicit purpose statement.

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 offers no guidance on when to use this tool versus alternatives like 'chain_deployments'. No exclusions, prerequisites, or comparison to sibling tools are provided, leaving the AI agent to infer usage context.

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