delete_bind_zone

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

The description goes beyond the destructiveHint annotation by explicitly stating the operation is irreversible and cascades to remove all records within the zone. This provides critical behavioral context that annotations alone do not convey, such as the full extent of the 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 compact and well-structured: a one-sentence purpose, a clear WARNING, and a sentence about cascading deletion. Every line adds valuable information without redundancy, making it appropriately sized 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?

The description provides all essential context for a delete operation: the resource, the irreversible nature, and the cascading effect on records. It does not need to explain return values since an output schema exists. This is complete for an agent to decide whether to invoke the tool and understand its impact.

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 schema description covers 100% of parameters, including the confirm safety gate and dry_run behavior. The description adds no additional parameter-specific information beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states exactly what the tool does: 'Delete a BIND DNS zone by ID.' It uses a specific verb and resource, clearly distinguishing it from sibling tools like create_bind_zone or update_bind_zone. The warning about irreversibility and removal of records further clarifies the scope.

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?

Usage is implied by the delete verb and destructive annotation, but there is no explicit when-to-use guidance or discussion of alternatives. It does not mention that this should be used only when a zone is no longer needed, nor does it contrast with update_bind_zone for modifications. However, the clarity of the purpose makes the intended usage fairly obvious.

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