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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds behavioral context: it returns 'unflagged tokens' with 'liquidity and latest scan risk', and notes the pairing is unique to Robinhood Chain. It doesn't describe pagination or output format, but with annotations covering safety, this is adequate.

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 sentences with no waste. The primary usage is front-loaded, the optional behavior is explained, and the unique-chain note is a single clause. Every sentence earns its place.

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?

For a single-optional-parameter read-only tool with no output schema, the description covers the key decision (pass vs omit stock) and the return content (unflagged tokens, liquidity, risk, counts). It doesn't describe output structure, but with no output schema and simple return semantics, this is a minor gap.

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 0%, so the description must compensate. It does: it explains the 'stock' parameter accepts a symbol like NVDA, SPY, TSLA, and that omitting it returns every stock with a count. This adds meaning beyond the bare schema, though it doesn't specify exact format or validation rules.

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's function: it lists memecoins quoted in tokenized stocks on Robinhood Chain, with a specific verb ('Pass a stock symbol') and resource ('tokens quoted in it'). It distinguishes itself from siblings by noting this pairing exists on no other chain, and the optional parameter behavior is explicitly described.

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 clear usage context: pass a stock symbol for trading, unflagged tokens with liquidity and risk; omit it for every stock with a count. It doesn't explicitly name alternative tools or when-not-to-use, but the context is clear enough for an agent to decide when to invoke it.

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