get_coin

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

With no annotations, the description must carry behavioral disclosure. 'Get' and 'snapshot' imply a safe read operation, and the returned fields are named, but it does not mention freshness, rate limits, auth requirements, or behavior for invalid ids.

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 front-loaded sentence with no wasted text. It packs the resource, returned fields, input format, and example into one concise statement.

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 simple one-parameter lookup tool, the description sufficiently explains the input identity and the snapshot contents returned. It lacks some operational context such as error handling or data freshness, but no output schema exists and the returned fields are at least listed.

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%, and the schema already documents the id parameter as a CoinGecko coin id with an example. The description adds an example ('ethereum') but does not add meaning beyond the structured 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?

The description states a specific verb and resource: getting a single coin snapshot, and names the returned fields (price, market cap, 24h/7d change). It distinguishes this from sibling list tools through 'single coin', though it does not explicitly contrast with get_real_market_cap or market_brief.

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?

Usage is implied by 'by CoinGecko id' and 'single coin', suggesting this is the lookup tool for one known coin. However, it does not explicitly say when to use it versus get_real_market_cap, list_top_coins, or market_brief.

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