iaas_delete_security_group

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so safety is covered, but the description adds nothing beyond that: it does not say what happens to machines still attached, whether deletion is asynchronous, or how the non-force path fails. The only added text is the endpoint path, which duplicates the annotation title.

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?

Front-loaded and short, but the first two lines are near-verbatim duplicates and the third line restates the endpoint already present in the annotation title, so roughly half the text is redundant rather than adding 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 delete with three parameters, annotations and schema carry most of the load and no output schema is needed. Still missing is any statement of failure behavior or dependency constraints (attached machines, non-on-demand groups), which is the main thing an agent would need before calling it.

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 the forceDelete parameter already carries a detailed caution about provider/VMware Aria Automation inconsistency. The description contributes no additional parameter meaning, which is the baseline expectation when the schema is fully documented.

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?

States a specific verb and resource ('Delete an on-demand security group with a given id') plus the underlying REST endpoint, so an agent can distinguish it from siblings like iaas_reconfigure_security_group or iaas_update_security_group. It does not explicitly name those alternatives, but the operation is unambiguous.

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 update/reconfigure, no prerequisites (e.g., security group must be an on-demand type, must not be attached to a machine), and no mention of the forceDelete escalation path. The repeated phrase 'on-demand security group' only hints at a scope restriction.

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