delete_firewall_rule

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

Beyond the destructiveHint=true annotation, the description explicitly states 'Mutating operation: permanently removes the rule from the controller,' disclosing that the operation is irreversible. It also surfaces the confirm=True gating requirement, which the annotations do not capture. This adds real behavioral context without contradicting the destructiveHint.

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 compact and front-loaded: a one-line purpose, a one-line mutation warning, then organized Args and Returns sections with clear defaults. The Args section partially duplicates schema text, but the overall length is still appropriate and scannable.

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 destructive 4-parameter tool with no output schema, the description covers the critical usage facts: confirm=True requirement, permanence, ID provenance, site default, and optional device targeting. The notable gap is the Returns section — 'Deletion status' is vague, and with no output schema the agent has no way to know the success/error shape to expect.

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 100%, so the schema fully documents all four parameters, warranting the baseline of 3. The description's Args block largely mirrors the schema verbatim (site default, confirm gate, device nullability); its only added value is provenance for rule_id (from get_firewall_rules).

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 states a specific verb and resource: 'Delete a legacy firewall rule.' The 'legacy' qualifier distinguishes it from sibling tools like delete_firewall_policy and creates/updates firewall rules/policies, so an agent can tell them apart at a glance.

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 implies its scope with the word 'legacy' and gives the source of the rule ID ('from get_firewall_rules'), but it never explicitly names alternatives such as delete_firewall_policy for the newer firewall-policy model, nor states when not to use the tool. Usage routing is left mostly to inference.

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