firewall_delete_group

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

With no annotations, the description must carry the full behavioral burden. It only mentions the ctx parameter for resource change notifications and the return status. It fails to disclose whether deletion is irreversible, whether associated rules are also deleted, or any prerequisites like the group being empty. This is a significant gap for a destructive operation.

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 well-structured with separate Args and Returns sections, and it is concise. It avoids redundancy and front-loads the primary purpose. The inclusion of ctx as a pseudo-parameter adds slight noise, but overall it is appropriately sized.

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 deletion tool, the description is incomplete. It does not mention the permanence of the action, whether rules within the group are affected, any constraints (e.g., group must be empty), or required permissions. The output schema exists but is not shown; the description only says 'Status message confirming deletion'. Given the complexity of firewall management, an agent needs more context to safely invoke this tool.

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?

The schema only defines firewall_group_id as a string with no description. The tool description adds critical semantics by stating it can be either a group ID or a description (e.g., 'web-servers' or UUID). This clarifies accepted formats and disambiguates the parameter beyond the raw schema. However, it also introduces a ctx argument not present in the schema, which could confuse the agent.

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 group') with a specific verb and resource. It is distinct from sibling tools like firewall_create_group or firewall_update_group, and the name itself is unambiguous.

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 does not explicitly state when to use this tool versus alternatives. It implies usage for deleting a firewall group but offers no exclusions or guidance on when to prefer this over other deletion tools (e.g., firewall_delete_rule). The context is obvious from the name, but explicit guidance is absent.

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