List App Store versions

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful shape information (newest-first ordering, state and attached build in results) but says nothing about pagination behavior or volume, even though a cursor parameter exists.

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?

Two sentences, zero filler, with what-it-does front-loaded and the use case following immediately. Every clause carries information.

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 6-parameter read tool with no output schema, the description covers purpose, ordering, and the notable fields returned, and the schema fully documents filtering and pagination. Only pagination behavior/first-page semantics are left unstated.

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 description coverage is 100%, including the enum values for state and platform and the cursor contract, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond implied ordering, so baseline 3 applies.

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?

States a specific verb and resource ('Lists App Store versions of an app') plus the sort order ('newest first') and the salient returned fields ('state and attached build'). The resource is cleanly distinct from sibling list_apps/list_builds, though it never explicitly names a sibling to contrast against.

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?

Gives a concrete downstream purpose: 'find the version ID for metadata, build selection and review submission', which implicitly routes the agent to update_version_localization, select_build_for_version and submit_for_review. It does not state any when-not-to-use condition or that list_builds is the separate resource for builds.

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