delete_tier1_gateway

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

The description discloses cascading removal of segments and NAT rules, and the handling of the locale-service, which goes beyond the destructiveHint annotation. It provides critical context about what happens during deletion.

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 description is concise, well-structured with a clear purpose, warning, behavioral details, and parameter explanations. Every sentence adds value without repetition.

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?

Given the output schema exists and the description covers deletion behavior, cascading effects, and parameters, the context is complete for an agent to use the tool correctly.

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?

With 0% schema coverage, the description compensates by explaining both parameters: tier1_id as the gateway ID and target as an optional manager target. This adds meaning beyond the schema's titles and types.

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 tool name and description clearly state it deletes a Tier-1 gateway. The warning about removing attached segments and NAT rules specifies the scope, distinguishing it from other delete operations like delete_segment.

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 description includes a warning about cascading deletions, implying when to use (when you want to delete a gateway and understand the consequences). It does not explicitly contrast with siblings like delete_segment, but the warning serves as a strong usage guideline.

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