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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by detailing the composite nature of the output and the pricing model (free tier then paid). No contradiction with annotations.

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, each serving a purpose: the first lists the comprehensive contents, the second positions its use case and pricing. No wasted 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?

Given the complexity of a composite report, the description outlines the major output categories and includes pricing details. With no output schema, this is sufficient for an agent to decide to invoke the tool and understand what it returns.

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% (the parameter 'token' is described). The description does not add new parameter-specific details beyond the schema, but it sufficiently contextualizes the purpose of the token (Robinhood Chain address).

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 provides the 'FULL token dossier in one call' and enumerates specific components like composite verdict, deployer rap sheet, token vitals, callers analysis, etc. It distinguishes itself from siblings by calling itself 'the single best first call on any Robinhood Chain token.'

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 positions the tool as the first call to make and notes a free tier of 25 calls per day, with paid beyond. It does not explicitly list when not to use or provide alternative tool names, but the context is clear enough for a decision.

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