delete_tier1_gateway

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

Annotations already show destructiveHint=true, but description adds irreversible nature, cascading deletion of segments and NAT rules, locale-service removal, and return type. No contradictions.

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?

Concise yet comprehensive: warning, prerequisites, behavior, return type, args. No redundancy. Front-loaded with '[WRITE]'.

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 tool's destructive nature and complexity, description covers all critical aspects: prerequisites, effects, return value. Output schema is present, though not detailed.

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, description fully explains tier1_id as 'Gateway ID to delete, as returned by list_tier1_gateways' and target as optional default. Adds necessary context.

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?

Description clearly states the tool deletes a Tier-1 gateway, warns about attached segments and NAT rules. Unique among siblings as the only delete gateway tool.

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?

Explicitly advises to run get_tier1_gateway and list_nat_rules first, and to confirm with user. Explains automatic removal of locale-service. No sibling confusion.

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