app_store_version_localizations_update_instance

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

With no annotations, the description carries the full behavioral burden. It conveys only that this is a PATCH (a mutation) and points at an OpenAPI schema for the body; it says nothing about required permissions, which fields are mutable, partial-vs-full update semantics, or what the response contains.

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?

It is short, but by under-specification rather than economy. The path is needlessly duplicated in parentheses, and the OpenAPI reference sends the agent to external documentation instead of front-loading what the tool does.

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 mutation endpoint with no annotations, no output schema, and an opaque free-form body, the agent is left unable to tell which localization fields it may update. Deferring entirely to an OpenAPI schema the agent may not have access to leaves the definition materially incomplete.

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 schema already documents both the id and body parameters, making 3 the baseline. The description's pointer to components.schemas.AppStoreVersionLocalizationUpdateRequest merely repeats the body property's own schema description, adding no syntax or field-level meaning.

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 is a raw endpoint restatement, "PATCH /v1/appStoreVersionLocalizations/{id}", duplicated verbatim in parentheses. It implies an update on a localization resource but adds no human-readable statement of purpose and does not distinguish this from the create/get/delete siblings beyond the operation identifier embedded in the name.

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?

There is no when-to-use guidance at all. Nothing tells the agent when to call update versus app_store_version_localizations_create_instance or _delete_instance, and no prerequisites or preconditions are given for a mutation endpoint.

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