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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful context — results are scoped to today and ranked by cross-platform price gap for a given district/neighborhood — but says nothing about result count, ordering guarantees, or how often the ranking refreshes.

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 front-loaded sentence with the resource, the scoping condition, and the ranking criterion, plus a short clarifying parenthetical. No redundant or filler wording.

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?

For a two-parameter read-only list tool with full schema coverage and no output schema, the description covers the essentials. It is still thin on what the list actually contains — item count, whether savings are absolute or percentage, and ordering — which an agent would want before selecting this over a comparison 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%, so both parameters (ilce, mahalle) are already documented, including the name-or-slug flexibility and the effect of mahalle on price and delivery. The description merely echoes the district/neighborhood scoping, adding no new syntax or format detail beyond the schema; baseline 3 applies.

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 resource (products with the largest cross-platform price gap today) and its scope (district/neighborhood), plus a parenthetical that it mirrors the site's home-page list. That distinguishes it reasonably from siblings like urun_karsilastir or hangi_uygulama_ucuz, but it never names an alternative explicitly, so it stops short of full sibling differentiation.

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: an agent can infer this is a discovery/browse tool for today's biggest savings. There is no statement of when to prefer it over urun_karsilastir (single-product comparison) or hangi_uygulama_ucuz (which app is cheaper), and no exclusions or prerequisites beyond the district requirement.

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