delete_firewall_rules

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

No annotations exist, and description does not disclose destructive nature, irreversibility, or potential impacts (e.g., affecting running instances). Only the word 'delete' implies mutation.

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?

Single concise sentence, but lacks structure for a tool with 3 parameters. Could benefit from explaining rule matching logic or providing examples. Not excessively long, but under-specified.

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?

With no output schema, no annotations, and 3 required params, description is insufficient. Missing impact, return values, error scenarios, and prerequisites for a deletion operation.

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 coverage is 100% with basic descriptions for each parameter. Description adds no extra meaning beyond schema. Baseline 3 is appropriate as schema carries the load.

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?

Description clearly states 'delete firewall rules of an instance' with a specific verb and resource. It distinguishes from sibling create_firewall_rules but lacks explicit differentiation from other delete-like tools.

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 guidance on when to use this tool versus alternatives, no prerequisites or context provided. The description is a bare statement of action without usage hints.

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