iaas_delete_compute_nat

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the generic 'Delete... with a given id' and the endpoint path — it does not warn that the deletion is irreversible or explain the forceDelete side effects (that caveat lives 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?

The first two lines say the same thing twice ('Delete a compute nat' / 'Delete compute nat with a given id'), wasting space on redundancy rather than front-loading useful detail. The only genuinely additive content is the trailing HTTP endpoint line.

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 single-resource delete with full annotation and schema coverage, the description is minimally sufficient — an agent can identify the operation and the required id. However it omits any caution about the destructive/irreversible nature and the forceDelete consequences, leaving that to the schema.

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 id, apiVersion, and forceDelete params are fully documented in the schema itself, including the warning about force-delete inconsistencies. The description contributes no parameter meaning beyond the phrase 'with a given id', so baseline 3 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 states the verb 'Delete' and the resource 'compute nat' with the qualifier 'with a given id', which is clear enough. But the first two lines are essentially a restatement of the tool name, so it adds little beyond what the identifier already conveys, and it never distinguishes this from sibling tools like iaas_get_compute_nat or iaas_reconfigure_nat.

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 tool versus siblings, no prerequisite or permission information, and no mention of the related reconfiguration/get operations. The agent is left to infer everything from the name and the raw HTTP path.

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