list_apps

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

With no annotations, the description should disclose behavioral details. It claims to list 'all apps' but the input schema reveals a limit parameter (default 50, max 200), which means it may not return all apps if there are more than 200. The description does not mention this limitation or any pagination behavior, making it somewhat misleading for a tool that says 'all'.

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?

The description is a single sentence, directly front-loaded with the action and resource, and includes only essential information (what is returned). No wasted words or redundant content.

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 listing tool with one optional parameter and no output schema, the description covers the core purpose and return fields. However, it fails to mention the 'all' vs. limit caveat, which is a notable gap in completeness for a tool that might be used to enumerate every app.

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?

The input schema fully documents the single 'limit' parameter with its description, range, and default. The tool description adds no extra parameter details, so the baseline of 3 applies since schema coverage is 100%.

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 uses the specific verb 'List' with a clear resource ('apps in your App Store Connect account') and enumerates the returned fields (name, bundle ID, SKU, App ID). This clearly distinguishes it from sibling tools like app_details, which likely targets a single app.

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 description clearly conveys that this is for getting an overview of all apps, which implicitly tells the agent when to use it (e.g., before drilling into app_details). It does not explicitly name alternatives or exclusions, but the context is clear enough for a listing tool.

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