subscription_images_v2_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, yet it discloses nothing beyond the HTTP verb. PATCH implies partial-update semantics, but the description does not state which fields are mutable, whether unspecified fields are cleared, what permissions are required, or what the operation returns for a mutating call.

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 short, but the path is needlessly duplicated in parentheses ('PATCH /v2/subscriptionImages/{id} (PATCH /v2/subscriptionImages/{id})'), which is pure redundancy and does not earn its place.

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 mutating tool with a nested, untyped body (additionalProperties: {}), no annotations, and no output schema, the description is inadequate: it offloads the entire request shape to an external OpenAPI document the agent may not have access to and explains none of the mutation's effects.

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% and both parameters are documented there, so the baseline is 3. The description's pointer to 'components.schemas.SubscriptionImageV2UpdateRequest' merely duplicates what the body parameter's schema description already says, adding no new parameter 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 essentially a restatement of the tool name as an HTTP route: 'PATCH /v2/subscriptionImages/{id}'. It conveys update semantics and the resource path, but no plain-language statement of what is being updated, and it does nothing to distinguish this from siblings like subscription_images_update_instance or subscription_images_v2_get_instance.

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 guidance on when to use this v2 endpoint versus the v1 subscription_images_update_instance, nor any mention of prerequisites, authorization, or state conditions. The agent is left to infer usage entirely from the name.

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