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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds nothing beyond that. It does not explain how the 5-year cap is enforced, what happens when no date arguments are supplied, whether the series is business-day only, or what the response contains.

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?

It is short and front-loaded, but the length comes from under-specification rather than efficiency. The raw endpoint `GET /v1/doviz/gecmis` and the phrase 'Her pakette' add no value an agent can act on.

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, 0% parameter coverage, and only a read-only annotation, the description carries the full explanatory burden and does not meet it. An agent could not determine date-window precedence or result shape from this text alone.

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 0% across four parameters, and the description gives no parameter meaning whatsoever. Critical ambiguities are untouched: whether `gun` (default 30) overrides or combines with `baslangic`/`bitis`, and what `kod` accepts beyond a 3-character code (the 5-year mention only loosely hints at the 1830 maximum).

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 text names the resource (TCMB buy/sell exchange rate history) and the granularity (daily, up to 5 years), so an agent can tell it is a historical-rates lookup. However, the body is essentially a verbatim repeat of the title plus an endpoint path, and it never distinguishes itself from siblings such as `doviz` (current rates), `altin_gecmis` (gold history), or `cevir_doviz` (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?

There is no when-to-use guidance at all: nothing says to pick this over `doviz` for current quotes or over `cevir_doviz` for conversion. The trailing fragment 'Her pakette' ('in every package') conveys no actionable selection criterion.

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