convert_currency

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

No annotations are provided, so the description carries the full burden: it usefully discloses that the rate comes from Huawei Cloud's own published rate rather than a market feed, which matters for quoting. It says nothing about rate freshness, rounding/precision, or what happens for unsupported currency codes.

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?

A single front-loaded sentence with the key constraint (USD amount, published rate) first and two concrete examples that earn their place. No filler.

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, the description should ideally hint at what comes back (converted amount, rate used), and it does not. Otherwise, for a simple two-parameter calculation tool with no annotations or nested objects, the essential information is present.

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 the description must compensate: it clarifies amount_usd is in USD and gives example currency codes (BRL, EUR), which adds real value. It still omits that currency is presumably an ISO code, its case sensitivity, and the set of supported values.

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?

States a specific verb (convert) and the exact resource (a USD amount) plus the rate source, so an agent knows precisely what this does. It is clearly distinct from every sibling in the list (quote, pricing, auth tools), though it never states the inverse direction is unsupported.

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 phrase 'Convert a USD amount' implies the direction (USD in, foreign currency out), which is a real usage constraint. But there is no explicit when-to-use, no note on when to call this versus just reading a price list, and no guidance on which currencies are accepted.

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