getCoinMarkets

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

Discloses read-only behavior, parameter roles, and that no API key is required. With no annotations, it covers key behavioral aspects, though could mention rate limits or errors.

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?

Concise paragraph with front-loaded purpose, use cases, sibling differentiation, and behavioral notes. Every sentence adds value.

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 full schema coverage, simple functionality, and no output schema, the description adequately covers purpose, usage, behavioral attributes, and parameter 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 100%, baseline 3. Description adds only marginal context beyond schema (e.g., 'canonical id', 'caps results'), but does not significantly enhance parameter understanding.

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 the tool returns specific markets and trading pairs with price and volume for a coin, and explicitly distinguishes it from getCoinExchanges for exchange names only.

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 explicit use cases ('where can I buy X', 'price on Binance'), directs to sibling for alternatives, and mentions prerequisites like canonical coinId resolution.

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