market_coingecko_derivatives_exchanges

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

There are no annotations, so the description carries full behavioral disclosure burden. It only says 'get list', implying a read operation, but does not disclose pagination behavior, output structure, or any rate limits. No contradictions with annotations since none exist.

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 sentence, extremely concise and front-loaded. It contains no filler and directly states the tool's purpose, which is appropriate for a simple list endpoint.

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?

The tool has no output schema and no annotations, so the description must inform the agent about expected returns and behaviors. It only states 'Get list of derivatives exchanges', omitting pagination details, the structure of each exchange object, and any special characteristics. This is insufficient for an agent to set expectations.

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 input schema fully documents all three parameters (page, order, perPage) with descriptions and defaults, so schema coverage is 100%. The description adds no semantic value beyond the schema, so the baseline score of 3 is appropriate.

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 'Get list of derivatives exchanges' clearly identifies the action (get list) and the resource (derivatives exchanges). It distinguishes from sibling tools like market_coingecko_exchanges by specifying 'derivatives', but doesn't elaborate on the exact scope or what qualifies as a derivatives exchange.

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 tool vs alternatives. The description does not mention any prerequisites, use cases, or exclusions relative to sibling tools such as market_coingecko_derivatives or market_get_exchanges.

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