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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new context: each call counts as one REST request (a quota/rate signal), prices are in TRY, and an empty symbol list returns every item from the source.

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?

Front-loaded with the core purpose, then the empty-list rule, examples and the REST-request cost — a sensible order. The closing English sentence largely duplicates the opening Turkish one, which is defensible for non-Turkish agents but is redundant text.

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?

With no output schema, the description carries the burden of describing returns, and it does state that buy/sell prices in TRY come back for the requested items. For a two-parameter read tool this is nearly sufficient, though the response shape (per-item fields) and the meaning of the source codes remain unstated.

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 already documents both `source` and `symbols`, including the empty-list behavior. The description contributes a longer example symbol vocabulary (ONS, parities, gold grades) but no explanation of what the twelve source codes mean or how they differ, leaving that to list_sources.

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 and resource set: it returns live gold, silver, FX and parity buy/sell prices for the Turkish market in TRY. That clearly separates it from get_price_history (historical) and calculate_value (computation), though it never names those siblings explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no routing to get_price_history, list_sources or calculate_value. The only usage-adjacent statement is that an empty `symbols` list returns everything, which is parameter behavior rather than tool selection advice.

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