getExchangeByID

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

No annotations provided, but the description fully covers behavioral aspects: 'Read-only', 'No API key required', and gives an example of the exchangeId parameter value. Discloses what data is returned (details, volume, etc.).

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?

Extremely concise: two sentences plus a short note on read-only and auth. Every sentence adds unique value—purpose, usage guidelines, parameter hint, and behavioral context. No wasted words.

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 2 parameters, no output schema, and no annotations, the description covers all critical aspects: purpose, usage examples, parameter example, read-only safety, auth requirements, and sibling tool differentiation. Completely adequate for an agent to select and invoke correctly.

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 baseline is 3. The description adds value by providing an example for exchangeId ('such as binance'), which clarifies the parameter's format beyond the schema. Quotes parameter is not elaborated further, but the example for exchangeId justifies a 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 retrieves details for a specific exchange: 24h volume, market count, trust score, links, and fiat support. It provides example queries ('tell me about Binance') and distinguishes from sibling tools like getExchangeMarkets and getExchanges.

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?

Explicitly states when to use ('tell me about Binance') and when to use alternatives: 'For the pairs traded there use getExchangeMarkets; find the exchange id first with search or getExchanges.'

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