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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral note that results are ranked by popularity and limited to multi-platform-comparable restaurants, but says nothing about result volume, pagination, or what happens when no restaurants match.

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 dense sentence with no filler, and the listing behavior plus the optional dish narrowing are front-loaded. It is compact enough that the 'birden çok platformda karşılaştırılabilen' qualifier takes a moment to parse, 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?

For a read-only, three-parameter list tool with full schema coverage and no output schema, the description covers purpose, ranking, and the dish filter adequately. Only edge-case behavior (empty results, result limits) is absent, which is minor here.

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 all three parameters are already documented, including that mahalle adjusts price and delivery scoping. The description only restates the optional dish filter with an example ('pizza') and adds no syntax or format detail beyond the schema, so 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 gives a specific verb and resource ('restoranları ... listeler') plus a distinguishing scope: only restaurants comparable across multiple platforms, sorted by popularity. That differentiates it from siblings like yemek_ara or search, though it doesn't name those alternatives explicitly.

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 implied rather than stated: use it for a district/neighborhood restaurant listing and optionally narrow by dish. There is no explicit 'use X instead when...' routing guidance against yemek_ara, urun_karsilastir, or fetch, so the agent must infer the boundary.

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