List beta app localizations

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds contextual detail about the type of data returned (feedback email, marketing URL, description per locale). However, it doesn't disclose pagination behavior or return format, though the schema's limit parameter partially addresses this. No contradictions with annotations.

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 a single sentence that is front-loaded with the main action and resource, followed by a concise parenthetical clarifying the content. It is appropriately sized with no wasted words.

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 simple list tool with detailed schema and annotations, the description provides enough context: it identifies the resource and the type of localized content. It doesn't explicitly mention that it lists all localizations across apps, but the tool name and filter parameters imply this. No output schema exists, but the description covers the return content sufficiently.

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%, so the baseline is 3. The description does not add parameter-specific information beyond the schema, but the schema already provides clear descriptions for limit and filters. The parenthetical in the description gives context for what the localizations contain, which relates to the overall purpose more than individual 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 clearly states the tool lists TestFlight (beta) app localizations and specifies the content (feedback email, marketing URL, description per locale). This provides a specific verb and resource, and effectively distinguishes it from sibling tools like list-beta-app-review-details.

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 implies the tool is for listing beta app localizations, which is clear from the context. It does not explicitly mention when to use it over alternatives, but no alternatives are needed given the unique purpose. The clarity of the verb and resource provides sufficient usage context.

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