List App Store Versions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. The description adds valuable behavioral context: it lists both released and in-progress versions, explains pagination via nextUrl, and describes the return structure. This adds meaning beyond the annotations without contradicting them.

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 highly concise: a one-sentence purpose followed by clear parameter bullet points and a code block for the return value. Every sentence is necessary and well-structured, with no wasted words. It is front-loaded with the most important information first.

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?

Given the tool is a simple read-only list operation with pagination, the description is complete. It explains parameters, pagination, and the full return shape (including field names and types). No output schema is provided, but the description compensates fully. The annotations cover safety and idempotence.

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 the description restates parameter details (appId, limit, nextUrl) with similar information. It does not add new constraints or examples beyond what the schema provides. A score of 3 is appropriate as the description adds marginal value over the schema for parameters.

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 explicitly states 'List App Store versions for an app (both released and in-progress)', which is a specific verb+resource combination. It distinguishes from sibling tools like asc_create_app_store_version or asc_update_app_store_version by focusing on listing, and clarifies the scope (both released and in-progress).

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 implies usage for querying app versions, and includes pagination details (nextUrl) that indicate how to handle large result sets. However, it does not explicitly state when to use this tool vs alternatives or provide exclusions. The context is clear but lacks direct guidance.

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