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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds nothing beyond that — no note on result volume, pagination, caching, or that only active exchanges are returned by default. Only the injected pricing boilerplate adds any non-schema information.

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 core purpose is a single front-loaded sentence, which is good. However, the appended pricing block is multi-line boilerplate that inflates the definition without helping tool selection, and the purpose sentence contains redundant bolding markup.

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?

An output schema exists and annotations cover the safety profile, so return values and side effects need not be explained. Still, the description omits the default status filtering behavior that shapes the output, and gives no sibling routing, leaving a modest gap for an otherwise simple lookup.

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 description coverage is 100%, so the single 'status' enum parameter (active/inactive, default active) is fully documented in the schema. The description contributes no additional semantics, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb ('query') and resource ('all the exchanges with ID and name'), and the title 'ID Map' confirms this is a lightweight identifier lookup rather than market data. However, it never distinguishes itself from siblings like get_coingecko_exchanges or get_coingecko_exchanges_id, which an agent must disambiguate among.

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 when-to-use context, no exclusions, and no routing to an alternative such as get_coingecko_exchanges for detailed data. The description also fails to mention the status filter (default 'active'), which materially changes the result set.

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