List version localizations

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network behavior are covered. The description adds the useful detail of which metadata fields are returned, but says nothing about pagination, result ordering, or behavior when the locale filter matches nothing.

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?

A single front-loaded sentence with the resource stated first and the returned fields enumerated after the colon. Nothing is wasted and no sentence needs to be reread.

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?

There is no output schema, so the description's field enumeration does real work in telling the agent what to expect back. For a two-parameter read-only list tool with full schema coverage this is nearly complete; only the sibling disambiguation and empty-result behavior are missing.

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 both parameters are documented in-schema, including the 'e.g. en-US' format and where versionId comes from (list_app_store_versions). The description adds no parameter-level meaning beyond the schema, so the baseline of 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 an App Store version's per-locale metadata') and enumerates the fields returned, so the agent knows exactly what data comes back. It does not, however, distinguish itself from the closely named sibling list_app_info_localizations, which an agent could easily confuse with version localizations.

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?

Usage is only implied: the required versionId and the phrase 'an App Store version's' signal that a version must already exist. There is no explicit when-to-use vs. when-not, and no mention of list_app_info_localizations (app-level localizations) or update_version_localization as the write counterpart.

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