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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds useful behavioral context beyond those hints by clarifying that the embedded tickers are only a sample and status_updates are included, which shapes agent expectations about the response without contradicting the annotations.

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 front-loaded with the core identity ('The full profile of one exchange') and then lists concrete fields, followed by succinct routing to alternatives. Every sentence contributes value; there is no repetition or filler.

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?

With only one well-documented parameter, an output schema present, and annotations covering behavior, the description supplies everything needed to select and invoke the tool correctly. It also covers the key decision boundaries against sibling tools, so no critical information is missing.

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 already fully documents the single id parameter with an example and explanation, so schema coverage is 100%. The description does not add new parameter-level meaning beyond reinforcing that the call targets one exchange, so the baseline 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 states a specific action and resource: retrieving the full profile of one exchange by its CoinGecko ID. It enumerates the contained fields and differentiates itself from sibling tools by naming what it is not, so an agent can distinguish it from list-style and ticker-specific siblings.

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 gives an explicit intended use ('Use it for venue due diligence') and names the exact alternatives for different needs: get_coingecko_exchanges for ranked lists and get_coingecko_exchanges_id_tickers for the complete paged pair list. This is clear routing guidance with no ambiguity.

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