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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds genuinely new context: cost ($0.05 or plan key) and the conditional nature of one section ('supply-forensics results if computed'), which tells the agent output varies by token.

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?

Front-loaded with the core purpose, then the enumerated contents, then the usage claim and cost note. The long content list is justified because it defines the tool's value, though the parenthetical cost/plan note is slightly buried and could be tightened.

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?

With no output schema, the description carries return-value disclosure and does so thoroughly by naming every report section. Still, it gives no sense of result size or formatting, and the pricing pointer to 'see instructions' is a dangling reference an agent cannot act on directly.

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% for the single 'token' parameter, so the schema already carries the syntax ('Token contract address 0x…'). The description adds no format, validation, or chain-scoping detail beyond what the schema states, making baseline 3 appropriate.

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?

States a specific verb and resource (a FULL token report) and enumerates its components: composite verdict, deployer record, launch history, token vitals, X callers with metrics, paper-basket status, supply forensics. The phrase 'in one call' and 'the single best first call' distinguishes it from narrower siblings like robinx_token, robinx_verdict, and robinx_deployer.

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 single best first call on any Robinhood Chain token' gives clear positive guidance on when to reach for it. It stops short of naming exclusions or the specific narrower siblings to use instead when only one slice is needed, so it lacks explicit when-not guidance.

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