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

Goes well beyond the readOnly/idempotent annotations: it discloses that dashboards may be lazily built on first request, that a no-key call is allowed, that every number carries a source and time, and that numbers failing a plausibility check are withheld rather than guessed. These are non-obvious behaviors an agent cannot get from the annotations.

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?

Purpose is front-loaded in the first sentence and the result/fallback behavior is efficiently explained. The trailing disclaimers ('No key', 'Not financial advice', 'Places no orders') are padding that dilutes an otherwise tight description.

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 burden and does describe the readiness field and the next_actions fallback, so an agent knows what to expect. It stops short of naming exact result fields, which is a minor gap for a one-parameter lookup tool.

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 single 'query' parameter is fully documented in the schema (100% coverage), and the description only repeats 'by ticker or name' without adding format, delimiter, or ambiguity-resolution guidance. Baseline 3 is appropriate when the schema carries the load.

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?

States a specific verb and resource (find a coin's dashboard) plus the lookup key (ticker or name), which is easy to distinguish from the sibling crypto_dashboard retriever. Sibling differentiation is only implicit, however, and the description never names alternatives.

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 explains what happens on a match (readiness flag) and on a miss (next_actions suggests alternatives), which implies discovery-first usage. But it never states an explicit when-to-use condition or contrasts itself with crypto_dashboard or search_markets.

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