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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds 'real-time' and 'current exchange rate' context, but does not disclose any additional behavioral traits beyond what annotations cover. With the annotations handling safety, the description adds marginal value.

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, front-loaded sentence that covers the core purpose without unnecessary elaboration. It is concise yet informative, though it could be slightly more structured by separating input details.

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 an output schema present, the description does not need to detail return values. It covers the primary use case and mentions real-time conversion. It does not explicitly address batch processing (comma-separated symbols) which is in the schema, but overall it is sufficiently complete given the richness of structured fields.

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 coverage is 100%, so the schema already documents all four parameters with descriptions and examples. The description does not add new semantic meaning beyond the schema; it only reiterates example symbols. Baseline 3 is appropriate.

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 it performs real-time currency conversion using Twelve Data, specifies the required inputs (forex pair symbol and amount) and the output (converted value at current exchange rate). This is a specific verb+resource combination that distinguishes it from sibling tools like exchange_rate or forex_pairs.

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 implies usage by specifying inputs ('pass a forex pair symbol...'), but it does not provide explicit guidance on when to use this tool versus alternatives like exchange_rate or forex_pairs, nor does it mention when not to use it.

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