vsz_create_domain

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

With no annotations, the description carries the full burden. It only says 'Create' but discloses no behavioral traits such as whether the operation is idempotent, required permissions, effects of duplicate names, or return value. This is minimal beyond the inherent mutation.

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 concise and front-loaded with the purpose. The Args block is efficient and every sentence earns its place, providing useful parameter explanations without fluff.

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 operation's complexity, the output schema covers return values, and parameter explanations are present. However, it lacks broader context like when to create a domain vs updating one, hierarchical implications, or success/failure behaviors. It is adequate but not thorough.

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 description coverage is 0%, but the description compensates by explaining each parameter: host as IP/hostname, name as domain name, description, and parent_domain_id for sub-domains. This adds meaning beyond bare property names, though it could include more constraints or formats.

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 'Create a new administration domain' with a specific verb and resource. It distinguishes from sibling tools like vsz_list_domains and vsz_get_domain, which read domains, whereas this tool creates.

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 guidance is provided on when to use this tool vs alternatives, prerequisites, or scenarios like creating sub-domains. It only states the action without contextual usage advice.

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