subscription_images_v2_delete_instance

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

No annotations are provided, so the description carries the full behavioral burden. It implies a destructive mutation via DELETE but does not state irreversibility, cascade/attachment effects, required permissions, or error behavior for a missing id — all critical for a delete operation.

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 the parenthetical literally duplicates the first string character-for-character, which is pure waste rather than added structure. Brevity is achieved by omission, not by tight writing.

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 destructive DELETE with no annotations and no output schema, the definition is too thin: it never says what resource the image belongs to, whether deletion is reversible, or what the agent should expect. The schema covers the id, but nothing else.

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?

There is a single parameter with 100% schema coverage, and the schema already documents 'id' as the requested resource id. The description adds nothing beyond this, so the baseline 3 for high schema coverage applies.

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 the tool name rendered as an HTTP route: 'DELETE /v2/subscriptionImages/{id}', repeated verbatim inside parentheses. It restates the name rather than explaining the purpose; an agent gets no more than it already infers from 'subscription_images_v2_delete_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 versus alternatives such as subscription_images_delete_instance, subscription_images_v2_update_instance, or the v1 delete. No prerequisites (parent subscription version, app association) or exclusions are stated.

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