Delete Firewall

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

The description simply reiterates the action implied by the tool name and the destructiveHint annotation. It adds no additional behavioral context such as whether associated rules are removed or if deletion is reversible.

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 one concise sentence that is front-loaded and contains no unnecessary words. It efficiently states the tool's purpose.

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 operation with one well-documented parameter and a destructiveHint annotation, the description is minimally sufficient. However, it lacks mention of side effects or dependencies, leaving some room for misinterpretation.

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 provides full coverage for the single parameter 'firewall_id' with a clear description. The tool description does not add further semantics beyond the schema, which is acceptable given the high schema coverage.

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 a firewall' uses a specific verb and resource, clearly distinguishing the action from sibling tools like vps_firewall_create or vps_firewall_list. It is unambiguous in intent.

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 usage guidance is provided. There is no indication of when to use this tool versus vps_firewall_delete_rule or vps_firewall_deactivate, and no mention of prerequisites or exclusions.

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