convert_currency

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

No annotations are provided, so the description must carry the behavioral burden. It only mentions the cost ('$0.001 USDC via x402'), but does not disclose return format, rate sources, whether it supports historical data, or any usage limits. This is minimal behavioral information.

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 very short, but the phrase 'Data & Weather tool' is filler that does not add value. While brevity is good, the sentence is under-specified and fails to include essential usage information, making it more of an incomplete note than a well-structured description.

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 generic schema, no annotations, and no output schema, the description leaves out nearly all contextual information needed to invoke the tool correctly. It does not explain exchange rate sources, supported currencies, output format, or any error conditions. This is critically incomplete for a tool that appears simple but has multiple implicit requirements.

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?

The input schema is generic with a single 'params' object described as 'Tool parameters as JSON object', providing no specific parameter names or types. The description does not compensate by mentioning required parameters like source currency, target currency, or amount. The tool name implies the purpose but not the exact parameter structure.

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 states 'convert currency' which is a specific verb and resource, but it does not distinguish this tool from sibling tools like 'currency_cross' or 'get_crypto_prices'. The additional label 'Data & Weather tool' is confusing and irrelevant to currency conversion, slightly muddying the purpose.

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?

There is no guidance on when to use this tool versus alternatives. No mention of comparing rates, using for fiat vs crypto, or any prerequisite like API keys. The cost note is the only extra detail, but it does not help select the tool.

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