crypto_search

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

With no annotations, the description carries full burden but only says 'search'. It omits behaviors like result format, pagination, API requirements, or error conditions. The agent cannot infer important behavioral traits.

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 a single concise sentence, but it lacks structure (e.g., front-loading key info). It is not verbose, but the extreme brevity leaves gaps.

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?

Given the presence of many crypto sibling tools and no output schema, the description fails to explain what the tool returns or how it complements others. The agent lacks context to use it effectively.

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 parameter 'query' has no schema description (0% coverage) and the description adds no clarification on expected input format (e.g., name, symbol, partial match). The agent receives no guidance beyond the parameter name.

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 states the verb 'search' and the resource 'cryptocurrencies' on 'CoinGecko', clearly differentiating it from other crypto tools like price or detail lookups. However, it could be more specific about the scope (e.g., search by name or symbol).

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?

No guidance is provided on when to use this search tool versus sibling tools like crypto_coin, crypto_price, or crypto_trending. The agent receives no cues about appropriate contexts or alternatives.

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