appstore__iap_urunler

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered and the description is consistent with it. The description adds no behavioral context beyond that (no pagination behavior, no return shape), so it does not exceed the annotation baseline.

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 zero waste; the scope qualifier that matters most for disambiguation is appended immediately.

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 simple two-parameter read-only list tool with full schema coverage and annotations, the description is sufficient; no output schema exists so return values need not be explained. Minor shortfall is the absence of any note on whether results are paginated via limit.

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% – both uygulama_id and limit are documented in the schema. The description adds no syntax, format, or default information for either parameter, so the 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?

Specific verb (listeler) plus resource (tek seferlik uygulama içi satın alma ürünleri) with an explicit scope qualifier (abonelik olmayanlar) that separates it from the sibling appstore__abonelikler. An agent can route between this and the subscription tool without opening either schema.

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?

The parenthetical 'abonelik olmayanlar' implies subscriptions live elsewhere, giving implied usage context, but no alternative tool is named and there is no when/when-not guidance. Adequate but with clear gaps.

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