opn_delete_firewall_category

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

No annotations provided, so the description carries full burden. It discloses savepoint protection, auto-revert behavior, system default category restrictions, and return type. This fully informs the agent about the tool's effects.

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?

Description is three sentences covering purpose, prerequisites, and behavior. It is front-loaded with the core action and efficiently conveys all necessary information without 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 one parameter, no annotations, and an output schema, the description fully covers behavior, preconditions, consequences, and tool interactions. It references sibling tools and explains the confirmation mechanism, making it complete for an 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?

Schema has one required 'uuid' parameter with 0% description coverage. The description mentions 'by UUID' and references opn_list_firewall_categories to find the UUID, adding value beyond the schema. However, it does not explicitly state the UUID format or source, so scores slightly below perfect.

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 'Delete a firewall rule category by UUID with savepoint protection,' specifying the verb (delete), resource (firewall rule category), and identifier (UUID). It distinguishes from sibling tools like opn_add_firewall_category and opn_list_firewall_categories.

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?

Provides explicit guidelines: reassign rules before deleting to avoid orphaned references, system default categories cannot be deleted, and changes auto-revert in 60 seconds unless confirmed with opn_confirm_changes. Suggests using opn_list_firewall_categories and opn_set_rule_categories for prerequisite steps.

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