coingecko_coin

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

No annotations provided, so description bears full burden. Mentions 'normalized' data and vs_currency enum support, but omits details on data freshness, rate limits, or safety profile. Adequate but not rich.

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?

Two sentences, front-loaded with verb and resource. No wasted words. Efficiently communicates purpose and key constraint.

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?

No output schema exists; description lists returned elements but not structure. For a single-coin profile, this is minimally sufficient but could be more complete with return format or example.

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 100%, so baseline 3. Description adds that vs_currency is a documented enum (not in schema) and id is the coin id. Does not add significant meaning beyond 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?

Clearly states it returns a CoinGecko coin profile with specific elements (profile, market stats, links, categories) for one coin id. Distinguishes from sibling tools like coingecko_markets (list) and coingecko_search (search) by focusing on a single coin.

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?

Provides a negative guideline ('not intended for real-time trading') but does not explicitly state when to use this tool versus alternatives like coingecko_coin_analysis or coingecko_markets. Lacks positive usage context.

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