get_compliant_exchanges

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds value by specifying the 'compliance matrix' filter, which is not inferable from the schema or annotations. It does not describe return format or pagination, but given the annotations, this is not a significant shortfall.

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?

Two sentences with zero wasted words. The core functionality is front-loaded in the first sentence, and the second sentence reinforces the purpose ('Essential for regulatory compliance'). This is appropriately concise and well-structured.

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?

For a tool with only two parameters (one optional), rich annotations, and no output schema, the description is complete. It tells the agent what the tool does, the key filter, and why it matters. Nothing essential for calling it correctly is missing. The agent can infer that the return is a list of exchanges without explicit statement.

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%, with both 'country' (ISO code example) and 'purpose' (enum values) clearly documented. The description adds no additional parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate. The compliance matrix mention is not tied to a specific parameter in a way that adds new semantic detail.

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 action ('Get exchanges'), the resource ('exchanges available in a specific country'), and the key filter ('CoinRebate compliance matrix'). This distinguishes it from sibling tools like get_exchange_fees and get_best_referral, which target different concerns. The note about regulatory compliance adds purpose and makes the tool's intent unmistakable.

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 implies usage context: use when you need compliance-approved exchanges for a country. While it does not explicitly name alternatives or exclusions, the clear focus on compliance and country-based filtering, combined with distinctly named siblings, gives an agent sufficient guidance to know when this tool is appropriate. The lack of explicit 'when not to use' is a minor gap but not misleading.

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