asc_update_metadata

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions updating on the 'currently editable version' but does not define what that means (e.g., required app state), nor does it discuss partial vs. full updates, error handling, or required permissions. For a mutation tool, this is insufficient behavioral context.

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 two sentences, front-loaded with the primary action and supported by the conditional guidance. Every sentence is essential, with no redundant or extraneous information.

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 6 parameters, no annotations, and no output schema, the description is too brief. It omits details on parameter interactions, default behaviors (e.g., locale default 'en-US'), error conditions, and expected output. For a tool modifying critical App Store metadata, more completeness is expected.

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 50%, with three parameters having descriptions (keywords, whats_new, create_version). The description lists the main fields but adds no additional meaning beyond the schema. For parameters like description and promotional_text, no constraints or examples are provided. The description provides marginal value over 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 states the tool's action ('Update App Store listing metadata') and lists the specific metadata fields (description, keywords, what's-new, promotional text). It also distinguishes itself from sibling tools like asc_bump_version or asc_submit_review by focusing on metadata updates.

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 provides explicit guidance on when to use the create_version parameter ('If no editable version exists, pass create_version to open a new one.'). It does not explicitly state when not to use the tool or compare with alternatives, but the context is clear for a metadata update scenario.

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