get_tcmb_snapshot

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

With no annotations, the description carries the full behavioral burden. It implies read-only retrieval and freshness via 'anlık' (instant/live snapshot), which is meaningful context, but discloses nothing about caching, update delay, rate limits, or auth requirements.

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 sentences, zero padding, with the resource scope front-loaded and the use case trailing. The enumerated indicator list is dense but each item is doing differentiating work.

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?

No output schema exists, yet the description compensates by listing nearly every returned field, so an agent knows what comes back. It falls short on return formatting and units (e.g. how currencies and the gold price are expressed) and on staleness characteristics.

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 tool takes zero parameters, so the baseline of 4 applies. There is no parameter semantics to add beyond what the empty schema already conveys.

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 a specific verb ('döndürür' / returns) and enumerates the exact resource contents: main FX rates (USD/TRY, EUR/TRY, GBP/TRY, CHF/TRY, EUR/USD), TCMB policy rate, US 10Y yield, and gram gold. The multi-indicator bundle scope clearly separates it from single-purpose siblings like get_tcmb_rate or get_exchange_rate.

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 closing clause ('Hızlı "Türkiye nasıl gidiyor" özeti için') gives one implied use case, so guidance exists but is thin. It never names an alternative (e.g. use get_tcmb_rate for only the policy rate) or states when this tool should not be used, leaving overlap routing to inference.

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