List app info localizations

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, and the description adds genuinely useful behavior: apps typically yield two info records, one live (READY_FOR_DISTRIBUTION) and one editable. That pre-empts an agent misreading a duplicated result set. It says nothing about ordering, pagination or which record is returned first, keeping it below 5.

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, front-loaded with the operation and its returned fields, followed by the one piece of context an agent would otherwise trip on. No filler or repetition of the title.

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?

With no output schema, the description compensates by naming the three returned fields and explaining why a result set may contain two records per locale. What's missing is how to tell the records apart programmatically (the state attribute is named but not tied to a response field) and any pagination note.

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 the schema (appId from list_apps, locale as en-US filter). The description's 'per-locale' phrasing loosely corroborates the locale filter but adds no syntax or edge-case detail beyond the schema, so the 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 an app's per-locale App Store info') and even enumerates the returned fields (name, subtitle, privacy policy URL), so the agent knows exactly what data comes back. It does not explicitly distinguish itself from the sibling list_version_localizations, which is the nearest source of confusion, so it stops short of a 5.

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 mention of an 'editable one while a new version is being prepared' implies the workflow context in which this tool matters, but it never states when to call this instead of list_version_localizations or update_app_info_localization. Usage is inferable rather than prescribed.

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