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

Annotations already declare this a read-only, idempotent, open-world, non-destructive lookup, so the safety profile is covered. The description goes beyond them by disclosing the selection gate for tickers (alive, $10K+ pool, not flagged HIGH or CRITICAL) and the fact that other-name holders are reported as a count and Solana holdings as marked name matches. That is real behavioral context about what gets filtered and how results are disambiguated.

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 opening clause is front-loaded with the verb and resource, and every sentence carries payload: input forms, gate criteria, and return shapes. The middle sentence is very dense (it packs the ticker gate, the count of competing names, and Solana name matches into one run-on), which costs a little readability. Appropriately sized for a multi-mode search tool.

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?

There is no output schema, so the description must explain returns, and it does reasonably: ids for fetch, plus learn:<slug> ids with a matching passage for word questions. For a single-parameter lookup with full annotation coverage this is nearly complete; only error/miss behavior (e.g. what an empty result looks like) is left unspecified.

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 and 0% schema description coverage, the description must carry the semantics, and it does: it defines the three accepted query shapes (address, mint, ticker) plus the additional natural-language question mode, and previews what each returns. It adds genuine meaning the bare 'query' string in the schema does not, though it doesn't spell out validation/error behavior for malformed inputs.

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 gives a specific verb+resource (find PumpPill's read for a query) and enumerates the exact input forms it accepts: 0x+40 hex Robinhood Chain address, base58 Solana mint, or a ticker like HOOD. It also names downstream siblings (fetch, /learn), so an agent can place it in the workflow without opening a schema. It stops short of 5 because it doesn't differentiate itself from rh_ticker_resolve, which appears to overlap on ticker handling.

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?

It establishes the workflow context clearly: this tool produces ids that are then consumed by fetch, and word-questions are routed to the lessons index at /learn 'instead'. That is a usable when-to-use signal. It lacks an explicit when-not-to-use statement or a contrast with the ticker sibling, so it is clear context rather than full routing guidance.

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