list_supported_exchanges

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

Without annotations, the description transparently explains the tool returns an object with `count` and `exchanges` array, with example values. No side effects are expected, and the return structure is fully disclosed. No contradictions.

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?

Description is concise, with two clear paragraphs: purpose and return format. No unnecessary words. Front-loaded with the main action.

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 zero parameters and no output schema, the description fully covers the tool's behavior: what it does, why use it, and what it returns. Complete for its simplicity.

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?

No parameters are defined in the input schema. The description adds no parameter info beyond schema (which is empty). Baseline for 0-param tools is 4.

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 lists supported exchange IDs via CCXT, with a specific verb ('List') and resource ('exchange IDs'). It explicitly differentiates from siblings by noting it provides valid IDs for other CCXT-backed tools like `get_exchange_markets`.

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?

Directly states when to use: 'Use this when you need to know which exchange_id values are valid for the other CCXT-backed tools.' It lists those tools, providing clear context. No explicit when-not, but the purpose is narrow enough.

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