create_email_zone

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

With no annotations provided, the description must disclose behavioral context, but it only states the creation action. It does not mention required permissions, side effects, return values, or any constraints beyond what the name implies, leaving the agent without important safety or workflow information.

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 a single concise sentence that front-loads the verb and resource. It contains no filler words and every word adds value.

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 tool has 8 parameters, nested objects, and no output schema, the one-line description is insufficient. It does not explain the zone creation workflow, required fields beyond schema, expected response, or how this zone type integrates with the email serving system.

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 coverage is 100%, so baseline is 3. The description adds no parameter-specific information, relying entirely on the schema for field meanings. It doesn't highlight any parameter relationships or domain-specific interpretation.

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 uses the specific verb 'Create' with the resource 'email zone', making the action unambiguous. It further clarifies the zone's purpose for 'serving ads in email newsletters', which distinguishes it from sibling tools like create_zone or vast_create_zone that target other zone types.

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 phrase 'email newsletters' provides clear context for when this tool should be used, differentiating it from general zone creation tools. However, it does not explicitly state when not to use this tool or name alternatives, so it lacks exclusion guidance.

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