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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the substantive behavioral context of what comes back (verdict, official address, ISIN, status, multiplier, pending corporate action, pool price/liquidity, premium vs Chainlink feed). The note that the Chainlink feed's value 'is not republished' is a genuinely useful disclosure about what the caller will and won't see. No rate limits or latency characteristics are mentioned.

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?

Two sentences, both front-loaded: the first establishes when to use it and the verdict space, the second enumerates the return payload. Given that there is no output schema, the enumeration earns its length rather than padding.

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 the return-value burden and does so fully: verdict options, official address, ISIN, status, multiplier, corporate action, pool depth and price, and premium relative to the Chainlink feed with its address and last-update caveat. An agent has everything needed to decide to call it and to interpret the result.

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%, so the schema already explains symbol, address and quote, including the ticker-vs-contract distinction and the quote dry-run flag. The description adds no parameter-level detail beyond referring to a contract and tickers in prose. Baseline 3 applies when the schema carries the parameter burden.

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 verb and resource: it determines whether a contract is the official Robinhood Stock Token or an impostor reusing the ticker, scoped to Robinhood Chain. It even enumerates the three possible verdicts, which pins the purpose down. It stops short of naming the sibling tools (scan_token, token_verdict, robinhood_token) it should be chosen over, so no explicit sibling differentiation.

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?

"Use this before touching a stock token" gives a clear trigger condition and places the tool in a pre-interaction verification workflow. There is no statement of when not to use it or which alternative tool handles adjacent cases, so the guidance is directional but not exhaustive.

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