Convert currency at TCMB rates

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds that cross rates are computed via TRY and that the bulletin for a given date or the latest bulletin is used, which is useful behavioral context beyond the annotations. It does not cover error handling or rate-limit behavior.

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?

Two concise sentences, with the core conversion scope front-loaded and no filler. Every clause adds relevant scope or date behavior.

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 existing output schema and annotations, the description covers the essential conversion behavior, supported currency relationships, and date default. It omits rate_type selection detail, but that is documented in the schema and not required for correct invocation.

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 80%, with descriptions for from, to, date, and rate_type, so the baseline is 3. The description clarifies the date fallback and cross-rate mechanism but does not add meaning beyond the schema for amount or rate_type.

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?

States 'Convert an amount between TRY and any TCMB currency, or between two foreign currencies (cross rate via TRY),' a specific verb and resource with unique cross-rate scope. This distinguishes it from the retrieval-oriented siblings get_exchange_rates, list_currencies, and get_rate_history even without naming them.

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?

Describes conversion scenarios and the date fallback ('Uses the bulletin for `date`, or the latest one'), but does not say when to choose this over get_exchange_rates or get_rate_history. Usage is implied rather than explicit, with no exclusions or named alternatives.

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