delete_terraform_alias

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 goes beyond that by warning that the endpoint can fail with 404 or empty results depending on edition/license/permissions — a failure mode an agent would otherwise misread as 'alias not found'.

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 short sentences, verb-and-resource statement front-loaded, endpoint last. The conditional-availability sentence is slightly vague ("some Community routes") but still earns its place as a caveat.

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 simple three-path-param delete with a full annotation set and no output schema, the definition covers identity, route, and failure caveats adequately. What is missing is whether deletion cascades or is recoverable, but destructiveHint already signals the risk.

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 0%, so the description must carry the load; the embedded path template (DELETE /project/{project_id}/inventory/{inventory_id}/terraform/aliases/{alias_id}) does map each of the three required params to its role in the hierarchy. It adds no type, format, or lookup guidance beyond that mapping.

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 terraform alias") and pins it down with the exact REST route, so an agent can distinguish it from create_terraform_alias, update_terraform_alias and delete_terraform_state. It never explicitly names those siblings, but the resource scoping 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?

The availability note (edition, license, permissions, 404s on Community routes) gives useful preconditions for attempting the call, which most delete tools omit. However, there is no guidance on when to prefer this over update_terraform_alias or how to verify the alias first via get_terraform_alias/list_terraform_aliases.

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