coingecko_markets

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

With no annotations, the description should disclose behaviors like data freshness, pagination limits, or nondestructive nature. It only states it returns normalized rows and is not for real-time trading, failing to explain potential rate limits or data source reliability.

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 concise sentences with no fluff. The first states the core function, the second adds relevant context about vs_currency and usage warning. Could be more structured but efficient.

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, and the description vaguely mentions 'normalized cryptocurrency market rows' without specifying fields like price, volume, or change. For a markets tool, this lacks return structure details, making it incomplete for an agent to understand what data to expect.

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 descriptions cover 100% of parameters. The description adds a note about vs_currency being a documented enum, but does not provide additional meaning beyond the schema's parameter descriptions.

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 clearly states it returns normalized cryptocurrency market rows from CoinGecko public pages. It specifies the verb 'returns', the resource 'market rows', and the source, distinguishing it from sibling tools like coingecko_coin or coingecko_search.

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?

The description mentions it supports the vs_currency enum and is not for real-time trading, but provides no explicit guidance on when to use this tool versus alternatives like coingecko_coin or coingecko_categories. Implied context but lacks clear exclusions.

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