create_sdn_zone

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states 'Create' and lists parameters, but fails to mention side effects, permissions required, idempotency, or any constraints. The output schema exists but is not referenced, leaving the agent uninformed about call results.

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 extremely concise: a single-line purpose followed by a bullet-style parameter list. Every sentence serves purpose, and the core action is front-loaded. No redundant or filler content exists.

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's complexity (7 parameters, 2 required) and the presence of an output schema, the description is incomplete. It lacks behavioral details, usage context, and constraints. While the output schema covers return values, the description does not address error states or prerequisites, leaving gaps for an agent.

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 has 0% description coverage, so the description must compensate. It lists parameters with minimal explanations (e.g., 'Zone ID', 'Zone type'), adding some value beyond the schema by enumerating allowed types for 'type'. However, most descriptions are tautological or vague, providing little semantic enrichment.

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 explicitly states 'Create an SDN zone,' which is a specific verb and resource. It clearly distinguishes itself from sibling tools like delete_sdn_zone and list_sdn_zones, leaving no ambiguity about the action performed.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no scenarios for appropriate use. It lacks explicit when-to-use or when-not-to-use context, making it difficult for an agent to decide between this and related tools like create_sdn_subnet or create_sdn_vnet.

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