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

The annotations already signal a read-only, idempotent, non-destructive tool. The description adds meaningful behavioral detail beyond that: results are 'unflagged' tokens, include liquidity and scan-risk information, and can return an aggregate count. No contradiction with annotations exists.

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 compact and front-loaded: it establishes the unique concept, gives the parameter behavior with examples, states the omit behavior, and explains why the tool matters. No sentence is wasted.

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 one-parameter, no-output-schema tool with rich annotations, this description is sufficient. It tells the agent exactly what input to provide, what the two output modes are, and what kind of data to expect.

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?

The schema provides only a bare optional 'stock' string with no description, and schema coverage is 0%. The description fully compensates by explaining both branches of behavior: passing a symbol like NVDA, SPY, or TSLA filters results to that stock, while omitting it returns a count per stock.

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 identifies the resource and behavior: listing memecoins that are quoted in tokenized stocks, with optional filtering by a stock symbol. The phrase 'pairing exists on no other chain' distinguishes it from sibling tools and highlights its unique scope.

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 gives explicit operational guidance: pass a stock symbol to see tokens quoted in it, or omit it to get every stock with a count. It does not explicitly name alternative tools or state when not to use it, but the usage context is clear.

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