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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and openness are covered. The description adds only a raw endpoint path and the opaque phrase 'Her pakette', neither of which tells the agent anything behavioral (units, currency basis, freshness, or that missing months are omitted).

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?

Very short and front-loaded with the data content. The trailing 'Her pakette' is unexplained filler, but there is no other padding.

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?

There is no output schema, so the description should explain what is actually returned — units of the endeks, whether changes are percentages, period labeling. It only echoes the field names and omits all of this for a data-retrieval tool.

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% and the single optional 'ay' parameter is documented in the schema as 'Kaç ay geriye (en çok 60)'. The description adds no meaning about the parameter, which is acceptable at full coverage but earns only the baseline.

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 (TÜFE/CPI) and enumerates the data it covers (index, monthly, yearly, 12-month average change), which is more than a bare title. However, there is no verb (get/list/retrieve), and it is largely a restatement of the title, so the agent must infer that this is a retrieval call.

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 statement of when to use this tool, when not to, or how it relates to any of the sibling tools (doviz, altin, vergi_maas, etc.). The agent gets no routing guidance at all.

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