firewall_delete_rule

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

With no annotations, the description carries the burden of disclosing side effects. It explicitly says 'Delete,' mentions the ctx context for resource change notifications, and promises a status message, but it does not state that the deletion is permanent or describe what happens if the rule or group does not exist.

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 compact docstring with the operation front-loaded in the first sentence, followed by concise parameter explanations and a return statement. There is no fluff or redundant restatement of the schema.

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?

This is a low-complexity tool with 2 required parameters and an output schema, and the description covers both IDs, their accepted formats, and the return type. What is missing is an explicit statement about irreversibility or permissions, but the destructive nature is clear from the verb 'delete.'

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 0%, so the description must compensate, and it does: it explains that firewall_group_id can be a name like 'web-servers' or a UUID, and firewall_rule_id is the rule ID to delete. It also defines the return value, though it lists a ctx parameter that is absent from the JSON schema.

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 opens with 'Delete a firewall rule,' a specific verb and resource that tells an agent exactly what operation this tool performs. The use of 'firewall rule' and the two identifiers distinguishes it from sibling tools like firewall_delete_group or firewall_create_rule, even without reading their schemas.

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?

No when-to-use guidance, prerequisites, or alternatives are provided; the description only restates the delete action. There is no hint that this should be used for removing individual rules while leaving the group intact, nor any pointer to list/get tools for obtaining valid IDs.

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