delete_address_rule

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

Without annotations, the description gives no insight into whether the deletion is permanent, what happens to existing matching rules, or any side effects, leaving the agent without critical behavioral context for a destructive action.

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 concise and front-loaded, consisting of a single clear sentence. However, it is so brief that it sacrifices useful operational detail.

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 delete operation with no output schema and no annotations, this description is under-specified: it omits prerequisites, effects, and expected return values, making it incomplete for an agent to use reliably.

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 input schema specifies rule_id as a required string, but the description ignores it entirely; with 0% schema coverage, the description should have explained the parameter's meaning and source but did not.

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 'Delete an allow/block rule' clearly states the action (delete) and resource (allow/block rule), distinguishing it from sibling tools like add_address_rule and list_address_rules.

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 provides no explicit guidance on when to use this tool, nor does it mention that rule_id should be obtained from list_address_rules, so the agent receives no usage context beyond the obvious.

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