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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description only needs to add context. It contributes the aggregation semantics and the 'tarihli' (dated) hint that results are time-bound, but says nothing about how fresh the data is, whether it is a cached snapshot, or how the frequency is computed.

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?

A single compact sentence with the scope stated up front and no filler. The parenthetical placement of the district breakdown makes it slightly less readable but nothing is wasted.

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 must convey the return shape; 'ne sıklıkla en ucuz çıktığı' implies frequency/ranking figures, which is reasonable but leaves the exact structure and the length of the comparison period unspecified. For a read-only, single-optional-param tool this is adequate but not complete.

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 coverage is 100% and the single optional 'ilce' parameter is documented in the schema as restricting to one district. The description's 'İstanbul geneli ve ilçe ilçe' adds the useful counterpart — that omitting the parameter yields the Istanbul-wide answer — but nothing beyond that 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?

States a specific resource and metric: how often each platform comes out cheapest, broken down Istanbul-wide and by district, with dates. This distinguishes it from sepet_karsilastir and urun_karsilastir, which compare single baskets/products rather than aggregate win-frequency. The only weakness is 'bugünkü karşılaştırmalarda', which is vague about the window being summarized.

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?

Usage is only implied: the aggregation framing suggests using this for 'which app is generally cheapest' questions rather than a concrete price check. It never explicitly says when to prefer this over the sibling comparison tools or when not to use it, so the agent must infer the routing.

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