vsz_list_dhcp_pools

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action 'List' and gives parameter definitions, but omits any information about pagination, error handling, authentication requirements, or safety guarantees. Even for a read-only operation, some behavioral context is expected.

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 highly concise with a single purpose sentence and a compact Args block. Every word earns its place, with no filler or redundant content.

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 low complexity, the presence of an output schema (so return values are documented externally), and a clear purpose with parameter definitions, the description is quite complete. It leaves only minor gaps such as explicit usage alternatives, but overall suffices for an agent to select and invoke the tool correctly.

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 provides zero descriptive coverage for parameters, but the description compensates by explaining 'host: vSZ controller IP or hostname' and 'zone_id: Zone UUID', giving essential meaning beyond the bare field names. This fully covers both parameters.

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 states 'List DHCP pools configured in a zone' with a specific verb and resource, clearly distinguishing it from the sibling tool vsz_get_dhcp_pool that retrieves a single pool. The scope (zone) is also specified, making the purpose unambiguous.

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 all DHCP pools in a zone, but it does not explicitly mention when not to use it, such as for a single pool, nor does it reference any alternative tool like vsz_get_dhcp_pool. The guidance is implicit rather than explicit.

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