iaas_delete_tag

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. Beyond the endpoint path, the description adds nothing behavioral — it does not mention that tag assignments are removed or that the call can be best-effort, even though ignoreUsage makes that possible.

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?

Three very short lines with the action and identifier front-loaded; nothing is padded. The heading line is redundant with the second sentence, which is the only inefficiency.

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-entity delete with full annotation coverage, complete param docs and no output schema, the definition is minimally sufficient. What is missing are the operational expectations: whether the tag must be unassigned first, failure behavior, and how to find a valid ID.

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 coverage is 100% and the schema fully explains id, apiVersion and ignoreUsage, including the un-assignment consequences. The description contributes no additional parameter meaning, so the 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?

States a specific verb and resource (delete a tag) plus the lookup key (by ID), so the operation is unambiguous. It does not differentiate itself from siblings such as iaas_get_tags or iaas_create_tag beyond what the name already conveys, and the first line merely restates the tool name.

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 iaas_get_tags_usage or iaas_create_tag, no prerequisite that the tag ID must exist, and no warning about the destructive consequence. The description offers only the HTTP route, leaving the agent to infer usage entirely.

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