priceConverter

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

No annotations provided, so description carries full burden. Declares read-only and no API key required. Gives clear constraints on parameter format. Could mention rate limits or error behavior, but adequate for a simple conversion tool.

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 examples, no filler. Purpose, usage guidance, and parameter nuance are front-loaded and efficient.

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?

Lacks output schema, but the conversion result is intuitive. For a simple tool, the description covers input constraints and usage adequately. Slight gap: no mention of what happens on invalid IDs (likely error), but acceptable.

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 coverage is 100% with descriptions for all 3 parameters. Description adds value by clarifying canonical slugs and that ticker symbols are rejected, and that amount defaults to 0. Builds on schema rather than repeating it.

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?

Clearly states it converts an amount between crypto/fiat at current rate, with examples. Explicitly differentiates from sibling 'getTickersById' for plain coin prices without amount.

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?

Provides explicit when-to-use (conversion with amount) and when-not-to (plain price without amount, use getTickersById). Also notes that baseCurrencyId and quoteCurrencyId require canonical slugs, not ticker symbols, and that no API key is needed.

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