qui_delete_instance

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

The annotation destructiveHint=true already signals destructive behavior. The description does not add context beyond this, such as irreversibility, required instance state, or effects on associated data. It merely restates the HTTP DELETE method, adding no new behavioral information.

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 a single sentence without fluff, efficiently conveying the endpoint and parameter-passing scheme. It is front-loaded with the action. It could be slightly more descriptive, but it is concise and to the point.

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?

The tool is relatively simple (generic arguments, destructive annotation, output schema exists). The description explains parameter structure but does not explicitly state the deletion effect or any preconditions. This is adequate for an API-savvy user who can infer from the endpoint, but it leaves gaps for completeness.

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?

With schema coverage at 0%, the description compensates by explaining how to structure the arguments: path variables directly, query values in arguments.params, and request body in arguments.body. This is valuable because the schema only has a generic 'arguments' object. It could be improved by explicitly mentioning the instanceID path variable.

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 specifies the exact DELETE endpoint, making it clear this deletes an instance. It names the HTTP method and resource, which distinguishes it from other instance-related tools. However, it's phrased as an API call rather than the intended effect ('delete an instance'), so it's not maximally clear.

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?

No guidance is provided on when to use this tool, prerequisites, or alternatives. It does not mention that this should be used to permanently remove an instance or that it should not be used for other operations. The description is purely instructional about the HTTP call.

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