Update App Info Localization

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

Annotations already indicate readOnlyHint=false and idempotentHint=false. Description adds critical behavioral details: partial update semantics, editable state requirement, error handling for missing fields and non-editable state, and return shape. This significantly complements 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?

Description is concise (approx. 150 words) and well-structured with sections for Args, Returns, and Error Handling. Every sentence adds value; no redundancy or fluff.

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?

Given moderate complexity (4 params, 1 required) and no output schema, description is fully complete: it explains the action, parameters, constraints, return format, and error conditions. No gaps.

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. Description adds value by noting that localizationId comes from 'asc_list_app_info_localizations' and by imposing a constraint: 'At least one of the optional fields must be provided', which is not in the schema. This clarifies usage beyond 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?

Description clearly states 'Update per-locale app-level metadata (name, subtitle, privacy policy URL)', specifying the action and the exact fields. It distinguishes from sibling tools like 'asc_update_version_localization' by targeting app info localization specifically.

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 explicit context: 'Only the fields you pass are updated. Only editable while the corresponding appInfo is in an editable state.' Includes error conditions (no updatable field, not editable). However, it does not explicitly state when to use this tool over alternatives, though the specificity implies it.

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