list_apps

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

The description claims 'List all apps' but includes a limit parameter that caps results (1-200), potentially misleading the agent. No annotations exist, so the description fails to disclose pagination behavior, authorization needs, or other side effects beyond returning metadata.

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 clear sentence, front-loading the purpose and distinguishing features. It is appropriately concise for a simple list tool, though it could be restructured to highlight the limit constraint.

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?

Despite having no output schema, the description mentions return fields (name, bundle ID, SKU). However, the phrase 'List all apps' conflicts with the limit parameter, and no pagination or error handling info is provided. For a tool with optional filters, the description lacks crucial behavioral context.

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?

With 100% schema description coverage, the schema already documents parameters (filter_name, filter_bundle_id, limit). The description adds no new parameter details beyond the schema, achieving only the baseline of 3.

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 verb (list) and resource (apps), distinguishing it from siblings like get_app (single app) and list_builds (builds). It specifies the returned metadata (name, bundle ID, SKU), making the purpose 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?

The description implies usage for listing apps but does not explicitly state when to use this tool versus alternatives like get_app for a single app or list_builds. No exclusions or best practices are provided, leaving the agent to infer from context.

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