delete_firewall_rule

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

Annotations already indicate destructiveHint=true, but the description adds valuable context beyond that: the deletion is irreversible and operates on the live appliance. This goes beyond the bare annotation and conveys the permanence and direct impact of the action. 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 a single concise sentence plus an explicit warning. It is front-loaded with the core action and includes no filler, earning every word.

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 rich schema (5 parameters, full coverage) and presence of both output schema and annotations, the description is reasonably complete for a delete tool. It adds the key caveat of irreversibility. It is not overly verbose, and the schema fills in operational details like rule_id sourcing and the confirm safety gate.

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% with detailed descriptions for each parameter (rule_id, confirm, dry_run, verify_descr, apply_immediately). Since the schema thoroughly documents parameter meaning, the description need not add more; baseline 3 is appropriate.

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 the action ('Delete a firewall rule') and the target resource ('from the live pfSense appliance'), making it distinct from sibling tools like update_firewall_rule or search_firewall_rules. The warning about irreversibility reinforces the specific nature of this delete operation.

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 no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as obtaining the rule_id via search_firewall_rules. The only contextual hint is the cautionary warning, but there is no 'when-to-use' or 'when-not-to-use' framing.

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