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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. Beyond that, the description discloses return payload contents — per-platform total, campaign, branch open/closed, minimum cart, platform link, and the literal 'bilinmiyor' marker when a delivery fee is unknown — which meaningfully compensates for the absent output schema.

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?

One dense but front-loaded sentence that leads with the core deliverable (total payable amount), then enumerates secondary return fields and input provenance. It is efficient, though the run-on structure packs multiple distinct ideas without separation, making it slightly harder to parse.

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 carries the burden of describing results and does so by enumerating returned fields and the unknown-fee convention. What remains unstated — behavior when a chain has no branch in the given district, or geographic limits implied by the 'ilce' parameter — is minor for a read-only price lookup.

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 each parameter already documents its source and format (e.g. urun as "menu|whopper" from yemek_ara/restoran_menusu output). The description's note about zincir and urun provenance largely restates what the schema says, and it says nothing about the optional 'mahalle' locality parameter, so it adds little beyond structured data.

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 comparison operation on a clearly bounded resource: the TOTAL payable amount for a single product across all platforms, explicitly including product price plus delivery fee. That scope separates it in spirit from sibling tools like sepet_karsilastir (cart) and hangi_uygulama_ucuz (which app is cheaper), though it never names a sibling to make the contrast explicit.

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?

It gives a valuable chaining prerequisite — the 'zincir' and 'urun' values must come from yemek_ara or restoran_menusu output — which tells the agent how to obtain valid inputs. However, it offers no explicit when-to-use versus when-not-to-use guidance against the sibling comparison tools, so the agent must infer the choice between single-product, cart, and savings comparisons.

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