list_apps

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

The description claims to list 'all' apps but the input schema includes an optional limit parameter (default 50, max 200), meaning the tool actually returns a limited page. This omission of pagination/limit behavior is misleading. Since no annotations are provided, the description carries the full burden and fails to disclose an important behavioral trait.

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 one short sentence, front-loaded with the verb, and contains no unnecessary words. It is appropriately concise and structurally clear.

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 list tool with no output schema, the description adequately states the resource, but it fails to mention the limit parameter's impact on pagination or that results are capped. This is a meaningful gap that could cause an agent to believe all apps are always returned. No mention of return format or authentication, but the primary omission is the pagination 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 documents the single 'limit' parameter with min, max, and default, so schema coverage is 100%. The description adds no additional parameter context, and its 'all' language conflicts with the limit's purpose. Baseline 3 is appropriate because the schema already handles parameter semantics.

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 clearly states the tool lists apps in the user's App Store Connect account, using the specific verb 'list' and resource 'apps', which distinguishes it from sibling tools like get_app or list_builds. The word 'all' slightly overpromises given the limit parameter, but the core purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like get_app for a single app or other list tools. There is no mention of use cases, prerequisite conditions, or exclusions, so an agent receives no decision support.

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