appstore__uygulamalar

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the payload shape (ad, bundle ID, App Store ID, birincil dil), which is useful context the annotations do not provide, though it says nothing about pagination or default ordering.

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?

Three short sentences, front-loaded with the listing action and followed by return fields and the reason to call it. Every sentence carries information with no filler.

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 compensates by naming the returned fields, and it explains the tool's role as an id source for sibling tools. Only minor gaps remain (pagination behavior, filtering semantics) for a simple two-parameter list 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 coverage is 100% and both parameters (limit, isim_filtresi) are documented in the schema itself. The description adds no semantics beyond that, so a baseline 3 is correct.

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 verb and resource ('App Store Connect hesabındaki uygulamaları listeler') and immediately enumerates the returned fields, so the agent knows exactly what this yields. The 'App Store Connect' scoping also implicitly separates it from the Play Store sibling (play__uygulamalar).

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 clear reason to call it first: 'Diğer araçların çoğu buradaki id değerini ister,' telling the agent this is a prerequisite for id-consuming tools. There is no explicit when-not or named alternative, so it falls short of a 5.

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