update_app_description

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Update,' implying mutation, but gives no details about permissions, side effects, validation requirements, or reversibility. This lacks the transparency needed for an agent to understand the operational impact.

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, focused sentence with no extraneous words. It front-loads the core information and is easily scannable.

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 update tool with two plain string parameters and no output schema, the description covers the essential purpose and scope. It does not mention prerequisites (e.g., the localization must already exist) or reference related tools, but it is adequate for the tool's straightforward nature.

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?

The schema provides 100% coverage with descriptions for both parameters ('New app description' and 'The app store version localization ID'), so the baseline is 3. The tool description's 'specific locale' reinforces the role of localizationId, but adds no additional semantic detail 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 clearly specifies the action (Update), the resource (app description), and the scope (for a specific locale), distinguishing it from sibling tools like update_whats_new and update_keywords. The verb+resource+scope structure is precise and unambiguous.

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 phrase 'for a specific locale' provides clear context on when to use this tool—when updating a localized description. It does not explicitly exclude alternatives or mention related tools, but the scope is sufficiently clear for basic usage.

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