List apps

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It states the action and filters but does not mention that the default limit is 50, that 'all apps' is subject to the limit parameter, or describe pagination or the response shape. The phrase 'List all apps' could be misleading given the default limit.

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 with the action front-loaded and filters appended. No filler or repetition; every word earns its place.

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 read-only list tool with fully documented parameters, the description is mostly adequate, but it omits the response format and does not clarify the relationship between 'all apps' and the limit parameter. With no output schema or annotations, the agent must infer return shape and default behavior.

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 describes all three parameters (contains match for name, exact match for bundleId, and default/max for limit), so the description adds no extra meaning beyond naming name and bundleId filtering. With 100% schema description coverage, baseline 3 is appropriate.

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 a specific verb ('List'), a precise resource ('apps in the App Store Connect account'), and notes optional filtering, making the core function immediately understandable. It does not explicitly differentiate from sibling tools like get_app or list_app_store_versions, so it misses the higher bar of naming alternatives.

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 implies the tool is used when you need the set of apps in the account and mentions optional name/bundleId filters. However, it provides no explicit guidance on when to choose this over sibling tools such as get_app (single app) or list_app_store_versions (versions), and no when-not-to-use conditions.

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