Reference interest rate and exchange rates

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds modest value by stating the data is current and sourced via BWO/SNB, but it does not describe pagination, units, or any time-dependence beyond the word 'Current'.

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 that covers both data modes with no filler. Every word contributes to the agent's ability to choose the right kind.

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?

For a simple read-only lookup with a full output schema and complete parameter schema, this description is sufficient. The only minor gap is that 'BWO' is not expanded in the description itself, though the schema's kind description also uses the acronym.

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 100%, so the schema documents all three parameters. The description adds the BWO/SNB context but essentially restates what the kind parameter's description already contains, so it provides no significant extra parameter semantics.

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 identifies the tool as providing two specific data products: the current BWO mortgage reference rate and SNB CHF exchange rates. It lacks an explicit retrieval verb, but 'Current ... or ...' makes the query intent clear and the two modes are distinct.

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 clearly separates the two use cases (reference interest rate vs exchange rate), which tells an agent when to select this tool. It does not mention when not to use it, but none of the sibling tools covers this data domain, so exclusion guidance is less critical.

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