import_exchange_rates

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

With no annotations, the description carries full behavioral disclosure and delivers richly. It details how daily rates are dated (validity window, not determination date), monthly averages (first of month), per-unit scaling (100/1000/10000), and the precision behavior (reported rather than rounded). It also discloses a refusal path for mis-paired payloads when `series` is supplied.

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 dense and front-loaded, stating the purpose first and then detailing parameter semantics and storage rules. Each sentence contributes new information, but the final sentence contains a slightly garbled phrase ('A published rate TILL cannot hold...') that marrs an otherwise tight structure. It remains concise for the amount of behavioral detail packed in.

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 absence of output schema and annotations, the description covers the key operational details: payload provenance, series validation, storage rules, scaling, and precision handling. It does not explain the `currencies` parameter or the return value/confirmation behavior, which would round out a fully complete picture. Overall, it is thorough enough for an agent to invoke correctly with minimal guesswork.

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 compensates well for the two most complex parameters: `payload` is defined as the exact response body from `describe_rate_feed`, and `series` is explained as a validation guard. The remaining parameters (`currencies`, `workspaceId`, `idempotencyKey`) are not elaborated, but they are either common conventions or optional; the description adds meaningful semantics where ambiguity is highest.

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 opens with a specific verb-resource pairing: 'Import a published BAZG rate payload into the rate store as `source='rate_api'`.' This clearly distinguishes it from sibling rate tools like `record_exchange_rate` or `describe_rate_feed` by specifying the exact input and storage action.

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 tool defines its primary use case: the `payload` is the verbatim response from `describe_rate_feed`'s named endpoint, making it clear when this tool is appropriate. It also explains the optional `series` parameter as a safety check for mis-paired payloads. It stops short of explicit exclusions or naming alternative tools, but the context is strong enough for an agent to route correctly.

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