vsz_list_domains

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

No annotations are provided, so the description must disclose behavioral traits itself. It only states 'List all' which implies a read-only operation, but it does not mention potential large result sets, pagination, authentication requirements, or any other behavioral nuances. This is minimal coverage for a description that carries full burden.

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 sentence for purpose and a minimal Args block. It is front-loaded and every element serves a purpose. No wasted words.

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 simplicity (one parameter), the description covers the essential purpose and parameter semantics. An output schema exists, so return values are presumably documented elsewhere. The description could mention that it returns domain object details, but the output schema covers this, so the description is adequately complete for its complexity.

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 defines 'host' as a string, but the description adds meaning by clarifying it as 'vSZ controller IP or hostname.' This extra context goes beyond the schema and helps the agent understand what value to supply. With only one parameter, this is sufficient.

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 a specific verb and resource ('List all administration domains'), which clearly distinguishes it from sibling tools like vsz_get_domain (retrieves a single domain) and vsz_create_domain (creates a domain). The scope 'all' adds precision.

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 implies usage when you need to list all domains, but it provides no explicit guidance on when to use this tool versus alternatives like vsz_get_domain, nor any exclusions or prerequisites. No alternative tools are mentioned.

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