Update app store version localization

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

Annotations indicate a non-read-only, non-idempotent mutation, and the description does not contradict this. The description adds context about what is updated (localized metadata) and points to a prerequisite, but it does not disclose side effects, permissions, or response behavior beyond the annotation flags.

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 are used with the action and resource front-loaded, followed by an essential instruction. Every word earns its place with no redundant content.

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 7-parameter mutation tool with no output schema and limited annotations, the description covers the core operation and the source of the required ID. The absence of return-value details is a minor gap, but the full schema coverage and basic behavioral context make it sufficient.

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% with descriptions for all 7 parameters, setting a baseline of 3. The description adds value by telling where to get the required 'appStoreVersionLocalizationId' and summarizing the updateable fields, which goes slightly beyond the schema.

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 uses a specific verb ('Update') with a clear resource ('app store version localization') and lists exact fields (description, keywords, URLs, what's new, promotional text). It distinguishes itself from sibling tools like 'update-app-store-version' by explicitly focusing on locale-specific metadata.

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?

Provides clear context: it updates localized metadata for a specific App Store version locale, and instructs the agent to obtain the localization ID from 'list-app-store-version-localizations'. However, it does not explicitly state when not to use this tool or mention alternatives, so it lacks full exclusion guidance.

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