Convert NOK to Foreign Currency

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable context: daily rates from Norges Bank, preservation of the NOK original in the response, and the behavior when amount_nok is omitted. It doesn't cover edge cases like rate unavailability, but that's acceptable given annotations.

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 three sentences, each earning its place: purpose and currencies, use-case context, and rate-only mode. It is front-loaded with the core action and remains compact without unnecessary 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?

The tool is simple (2 params, 1 required) and has an output schema, so return values are covered. The description provides all essential context: data source, use case, currency support, and a special mode. No gaps remain for a tool of this complexity.

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 both amount_nok and to_currency are already well-documented in the schema. The description mostly restates these details (supported currencies, omitting amount_nok) and adds the rate-source context, but doesn't significantly extend parameter-level meaning beyond what the schema provides.

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 NOK amounts to specific foreign currencies (EUR, USD, GBP, SEK, DKK) using Norges Bank rates. It is distinct from all sibling tools, which focus on company, person, or AML data, and the verb 'convert' precisely describes the 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?

It provides clear context on when to use the tool: to express Firmaradar's NOK-reporting financial figures in another currency for international workflows. It also explains how to fetch just the current rate by omitting amount_nok, but it doesn't explicitly state when not to use it or mention alternatives, though none exist among siblings.

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