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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds useful behavioral context by calling it 'the same read the public site performs' and indicating it returns recorded history, which helps the agent understand expected side effects and data freshness.

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?

Three concise sentences with no filler: the first declares the action and return fields, the second states accepted input formats, and the third grounds it in a familiar public-site behavior. Every sentence earns its place and key info is front-loaded.

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 one parameter and no output schema, the description sufficiently covers what the tool does, what input it takes, and what data will be returned, including the possible 'no outcome recorded' label. No critical call-time detail is missing.

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 for the only parameter is 100%, so the schema already documents accepted formats and provides an example. The description reinforces the accepted address types but adds no additional semantic meaning beyond what the schema already states, meeting the baseline.

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 a specific action (look up one token) and resource (GROUNDTRUTH records), and enumerates exact returned data: outcome label, liquidity, market cap, holder counts, and launcher wallet. It explicitly distinguishes itself as a single-token lookup, which separates it from batch/screen siblings.

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?

Clear context is provided: this is for a one-token lookup, accepting either Solana mint or Robinhood Chain address, and it matches what the public site does when pasting a contract. It does not explicitly name alternatives or when-not-to-use cases, so it falls short of a 5.

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