create_zone

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

Beyond annotations which indicate openWorldHint but no destructive hint, the description reveals a key behavioral trait: the preview mode that returns non-executing results when confirm is missing or false. This adds significant context.

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 with no extraneous words. The critical information (what it does, the confirm gate) is front-loaded and efficiently conveyed.

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?

Given the parameter descriptions and the preview/execute distinction, the description provides complete guidance for an agent to understand the tool's behavior and anticipate outcomes (preview or creation). No output schema is needed.

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 already describes all parameters (100% coverage). The description adds essential semantic context about the confirm parameter's dual role (preview vs execution), which is not evident from the schema alone.

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 the tool adds a new domain (zone) to an account, using the verb 'add' and specifying the resource. It distinguishes itself from sibling tools like create_dns_record by being zone-specific.

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?

The description explicitly explains the human-approval gate: use confirm:true for actual execution, omit or false for preview. This provides clear when-to-use guidance, though it does not explicitly contrast with alternative methods for zone management (which are not applicable).

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