delete-sec-rule

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

With no annotations provided, the description fully carries the burden. It declares 'WRITE OPERATION: changes PCE state,' which is a critical side-effect disclosure, and goes further to warn that in gated clients the call pauses for user approval and 'must not be retried while waiting.' This is exemplary behavioral transparency for a mutation tool.

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?

Four short sentences with no filler. The core action, sibling alternative, side-effect warning, and retry instruction each earn their place and are ordered logically, from definition to operation to caveats.

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 single-parameter delete tool with no output schema, the description supplies all essential context: what it does, when to use, side effects, and client-specific approval behavior. The only minor omission is what happens after approval, but that can be inferred from the call completing normally, so this is essentially complete.

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 only parameter, href, has a 100% descriptive schema including an example. The description adds no extra parameter-level semantics, so it correctly rests on the schema. Baseline 3 applies by design.

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 a specific verb and resource: 'Delete a single allow rule from a ruleset, leaving the rest of the ruleset intact.' It explicitly differentiates from the sibling delete-deny-rule by naming it and stating the condition ('For deny rules use delete-deny-rule'). This leaves no ambiguity about what the tool operates on.

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?

It explicitly tells the agent when to use this tool ('allow rule') and when not to ('For deny rules use delete-deny-rule'). The phrase 'leaving the rest of the ruleset intact' also signals that this tool is for single-rule deletion rather than deleting the whole ruleset. This is direct, actionable usage guidance.

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