Convert currency at TCMB rates

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

Annotations already cover safety (readOnlyHint) and scope (openWorldHint), but the description adds two real behavioral facts: rates come from the official TCMB bulletin, and cross-currency conversions are computed via TRY rather than from direct pairs. It omits notable operational traits such as what happens on weekends/holidays when TCMB publishes no rate, and whether the result is rounded.

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?

One sentence, front-loaded with the verb and the currency scope, then the rate source and date qualifier. There is no filler or repetition of the title.

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 has five parameters, no output schema, and no nested objects, so the description must carry some of the return-shape burden; yet it never says what comes back (converted amount, effective rate, date used). It also leaves the non-publication-day behavior unaddressed, which matters for a rate lookup keyed on a date.

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 each parameter is already documented, including the rate_type enum and its default. The description only adds the 'via TRY' triangulation note and the date framing; it does not enrich amount, from, or to beyond what the schema says, so baseline 3 applies.

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 names a specific verb (Convert) and resource (an amount between currencies), and adds precise scope: TRY against any TCMB bulletin currency, or foreign-to-foreign via TRY, using official TCMB rates for a date. This is enough to separate it from the sibling get_exchange_rates, which plainly returns rates rather than performing conversion.

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 when to use it (you want a converted amount rather than a rate table), but it never explicitly says 'use get_exchange_rates instead if you only need the quote' or states prerequisites. The 'for a date' phrasing also hints at historical usage without clarifying behavior when no date is given, so guidance is inferable rather than stated.

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