calc_currency_convert

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only mentions Decimal precision, leaving unclear how rates are sourced, whether 'live' and 'date' affect results, or what edge cases exist. This is insufficient for a 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?

The description is short, but 'COMPUTE.' is filler and does not earn its place. The meaningful part 'Convert currencies with Decimal precision.' is concise and front-loaded, so overall it is acceptable but not exemplary.

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?

The tool has five parameters, no output schema, and no annotations. The description provides almost no context about expected inputs, return values, rate behavior, or error conditions. It is far from complete for an agent to invoke it confidently.

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%, and the description does not explain any of the five parameters. It does not clarify 'amount', 'from_currency', 'to_currency', 'date', or 'live'. The description adds no parameter-level meaning beyond what the schema field names imply.

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 clearly states the tool converts currencies and highlights Decimal precision, which is a specific action on a specific resource. It distinguishes itself from the financial calc sibling tools, though the leading 'COMPUTE.' adds no purpose information.

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?

No guidance is provided on when to use this tool versus alternatives such as calc_metric or calc_npv. The intent is implied by the tool name and description, but no explicit context or exclusions are given.

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