convert_currency

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

With no annotations, the description carries the transparency burden. The verb 'Get' and the word 'estimation' convey a read-only, approximate result, but it does not disclose whether authentication is required, whether both conversion directions are supported, or what rates/fees apply.

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 a single sentence that states the tool's purpose immediately, with no filler or repetition of structured fields.

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 no output schema or annotations, the description should clarify the return value and conversion direction; it does neither. The phrase 'between fiat and Bitcoin' leaves ambiguous whether the input is fiat converted to BTC or BTC converted to fiat, and the expected output format is unspecified.

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 amount and currency already documented in detail, so the baseline is 3. The description adds the fiat/Bitcoin context but does not clarify conversion direction or semantics beyond the schema.

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 uses a specific verb ('Get') and resource ('currency conversion estimation') and clearly names fiat and Bitcoin. It is clear and distinguishable from siblings like get_realtime_price, though it does not explicitly call out alternatives.

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 provides no guidance on when to use this tool versus alternatives such as get_realtime_price or get_supported_currencies. It simply states what it does without any when/when-not guidance.

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