delete_firewall_rule

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

The description goes beyond the 'destructiveHint: true' annotation by explaining the irreversible nature: 'IRREVERSIBLE: the rule stops applying immediately, changing what traffic is allowed.' It also details the confirm parameter behavior (omit/false leads to refusal). No contradiction with annotations.

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 (three sentences), front-loaded with the purpose, and each sentence adds distinct information: purpose, scope, irreversibility, confirm usage, and parameter origins. No redundancy.

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 no output schema, the description does not need to explain return values. It covers the core operation, side effects, and prerequisites. It could mention that the removal is reflected in subsequent get_firewall calls, but this is implied. Overall, it provides sufficient context for an AI agent.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds value by specifying that 'id and ruleId both come from get_firewall,' providing a data source hint. For the confirm parameter, the schema already explains behavior fully, so no extra credit needed.

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 clearly states 'Remove a rule from a cloud firewall,' which is a specific verb+resource. It implicitly distinguishes from the sibling tool 'add_firewall_rule' by being the inverse operation, and the tool name itself indicates deletion.

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 provides necessary prerequisites ('Requires scope services:write') and operational guidance ('Pass confirm:true only after the user has explicitly approved'). It also explains that id and ruleId come from get_firewall, aiding source selection. However, it does not explicitly state when not to use this tool versus alternatives like add_firewall_rule, though the name makes it clear.

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