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

Annotations already indicate readOnlyHint and non-destructive behavior. The description adds valuable context beyond annotations, such as the $0.05 cost, the off-market extraction history, identity data, and the caveat that it's not a buy call. This gives the agent a richer understanding of tool behavior.

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 fairly concise, packing key information (holder set, measured record, identity, cost, signal ambiguity) into a few sentences. The front-loading is effective, though the mention of 'paid $0.05 — see instructions' adds minor redundancy.

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 simple input (one required parameter, no output schema), the description adequately explains what the tool returns (wallets with specific attributes and identity). It covers the core output and signal interpretation, making it mostly complete for an experienced agent.

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?

With only one parameter (token) and 100% schema description coverage, the schema already fully documents the parameter. The description does not add any additional meaning or format details for the parameter, so it meets the baseline but does not exceed it.

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 defines the tool's purpose: listing wallets from a token's notable holder set that have a measured record on Robinhood Chain, with specific data like extraction history and identity. It distinguishes from sibling tools by focusing on cross-referencing holders with off-market data.

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 provides some guidance, noting the signal is ambiguous and not a buy call, and mentions the cost. However, it does not explicitly state when to use this tool over alternatives or identify preconditions, leaving some ambiguity for the agent.

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