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

With no annotations, the description carries the full burden and does well: it discloses the data sources combined (price action, news sentiment, Fear & Greed), the shape of the result (two ranked lists with scores and reasons), and an explicit cost of 3 credits per call. It omits read-only status and any auth/rate-limit context, which slightly limits the score.

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?

Four tight sentences, front-loaded with the purpose, then data sources, return shape, parameter behavior, and cost. Every sentence adds distinct information; nothing is redundant.

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 no-output-schema, no-annotation tool, the description covers return shape, data provenance, defaults, and cost, which is enough for an agent to call it correctly. The gap is the unexplained deep/universe parameters, but these are optional knobs with schema-level hints.

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 coverage is 67%, above the half-way mark, so the baseline of 3 applies. The description only illuminates the ids parameter ('scan the top coins or pass your own list') and says nothing about deep or universe, whose meaning is left entirely to the schema.

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: scans the market for coins likely to run vs. showing warning signs, and names the two output lists. It is clearly distinguishable from data-lookup siblings like crypto_markets or crypto_coin, though it never names an alternative directly.

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?

Gives implied usage (scan top coins by default, or pass your own list) but no explicit when-to-use vs. when-not, and no routing against the many crypto_* siblings. An agent must infer that this is the analysis/signal tool rather than the raw-data tools.

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