zones_delete_zone

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It indicates a destructive delete operation and acceptable ID formats but fails to describe side effects, reversibility, permissions, or error scenarios (e.g., zone not found, zone in use).

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?

A single sentence of 16 words that conveys all essential information without fluff. The structure is efficient and front-loaded with the primary action.

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 basic function and acceptable IDs. It mentions the underlying webservice call for debugging context. However, it lacks details on error handling, return values (though output schema exists), and prerequisites. Adequate but not comprehensive.

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 has one parameter 'zone_id' with no description (0% coverage). The description adds value by clarifying that the ID can be a 'zone helper id or `zone.<id>`', but does not specify the exact expected format or provide examples. It partially compensates for the missing schema description.

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 clearly states 'Delete a zone', a specific verb+resource. It also mentions the underlying WS call and acceptable ID formats (zone helper id or 'zone.<id>'), distinguishing it from create, update, get, and list siblings.

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 explicit when-to-use or when-not-to-use guidance is given. However, the purpose is clear, and sibling tools have distinct actions (create, update, get, list), allowing the agent to infer context. Additional prerequisites or error conditions are not mentioned.

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