Delete Firewall

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

Adds the key precondition that the firewall must be detached before deletion, which is valuable beyond the destructiveHint annotation. No other side effects mentioned, but the prerequisite is critical.

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?

Two sentences, no wasted words. Immediately states action then precondition – efficient and front-loaded.

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 simple delete tool with one parameter, the description covers the crucial prerequisite. Lacks details like error behavior if still attached, but adequate given annotations and schema richness.

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 description coverage is 100% (id described as 'Resource ID'). The description adds no further parameter guidance, so baseline score of 3 applies.

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?

Clearly states 'Delete a firewall' – specific verb and resource. Distinguishes from siblings like hetzner_remove_firewall by the action (delete vs remove).

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 a prerequisite: firewall must be removed from all resources first. However, does not explicitly compare to hetzner_remove_firewall or indicate when to use delete versus remove.

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