iaas_delete_machine

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the HTTP verb and path: it does not say what state the machine is left in, whether disks are removed, or that deletion is irreversible. The forceDelete caveats live only in the schema.

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 and front-loaded, but the three lines are near-duplicates of one another and of the title; the repetition does no work and crowds out the behavior notes an agent actually needs.

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, open-world delete on a cloud machine, the description supplies no lifecycle context: no ordering relative to power-off, no note about dependent resources, no confirmation of what is returned (there is no output schema). Annotations and schema cover the mechanical bits, but a call this consequential deserves more than an endpoint echo.

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 explains id, apiVersion and the forceDelete inconsistency warning. The description contributes no parameter meaning beyond the {id} path placeholder, which is the baseline 3 case.

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 names a specific verb and resource ('Delete Machine with a given id'), which is clearer than the bare name, but it does no work to distinguish this from the many other iaas_delete_* siblings. It restates the title and endpoint path rather than defining scope or consequences.

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 delete a machine versus alternatives like iaas_unregister, iaas_suspend_machine, or iaas_power_off_machine, nor any precondition such as the machine needing to be powered off first. The agent is left to infer everything about selection.

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