get_exchange_rate

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

With no annotations, the description must disclose behavioral traits on its own. It only mentions 'real-time' and the supported pairs, omitting the return format, rate type, or any limitations such as delayed data or API restrictions, leaving the behavior under-specified.

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 sentence that directly conveys the purpose and supported pairs, with no filler or repetition. It is well-structured and front-loaded with the main action.

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?

This is a simple tool with one parameter, but the absence of an output schema means the description should explain what data is returned. It does not, and it also lacks any mention of the response format or the source of the rates, making the description incomplete for robust agent decision-making.

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?

The single 'pair' parameter is fully described in the schema with an enum and description, and the description simply repeats the allowed values without adding semantics. Since schema coverage is 100%, a baseline of 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 explicitly states the tool 'fetches real-time exchange rate information' (실시간 환율 정보를 가져옵니다) and names the specific currency pairs (USD/KRW, JPY/KRW). This clearly defines the verb+resource+scope, distinguishing it from sibling tools that fetch other asset prices.

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 the tool is for exchange rate lookups but does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools for other asset types. An agent must infer usage from the tool name and domain rather than from direct instructions.

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