iso_delete_iso

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

There are no annotations, so the description must carry the burden of explaining the operation's effects. It only repeats the delete action and promises a 'Success message'; it does not disclose irreversibility, permissions required, or any side effects on the ISO resource.

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 compact and front-loads the operation, with a short Args/Returns structure. It avoids unnecessary prose, though the Args line adds only marginal 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?

For a destructive one-parameter tool with no annotations, the description is minimal: it omits how to discover valid ISO IDs, whether deletion is permanent, and any consequences. The simple return note does not compensate for the missing operational context.

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 0% schema description coverage, the description must define the parameter, but 'The ISO ID to delete' mostly restates the property name iso_id. It adds no format, source, or constraints beyond the schema's string type.

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 identifies the action ('Delete') and the resource ('an ISO image'), which distinguishes this tool from its iso_* siblings. The purpose is unambiguous and requires no inference.

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 gives no guidance about when deletion is appropriate, how to obtain the iso_id (e.g., via iso_list_isos), or whether there are preconditions such as detaching the ISO from an instance. It neither names alternatives nor states exclusions, so the agent gets no usage direction.

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