get_real_time_currency_conversion

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

The annotation 'readOnlyHint: true' already indicates this is a safe read operation. The description adds no behavioral context beyond the basic purpose—it doesn't mention rate limits, data sources, accuracy, or any constraints like supported currencies. With annotations covering safety, the description adds minimal value, scoring a baseline 3.

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, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 the tool has 5 parameters with 0% schema coverage, an output schema (which helps), and annotations covering safety, the description is incomplete. It lacks parameter explanations, usage context, and behavioral details, making it insufficient for an agent to fully understand how to use the tool effectively.

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 0%, so parameters are undocumented in the schema. The description provides no information about parameters, failing to compensate for the coverage gap. It doesn't explain what 'from_', 'to', 'amount', 'precision', or 'params' mean, leaving their semantics unclear.

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 'Get real-time currency conversion' clearly states the verb ('Get') and resource ('real-time currency conversion'), making the purpose understandable. However, it doesn't differentiate this tool from sibling tools like 'get_last_forex_quote' or 'get_last_quote' that might also provide currency-related data, leaving the distinction unclear.

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. With multiple sibling tools that could handle currency or forex data (e.g., 'get_last_forex_quote'), there's no indication of when this specific conversion tool is appropriate, making usage ambiguous.

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