iaas_get_zones

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing about pagination defaults, result size, or whether zones are scoped to the current org/project — the only remaining behavioral questions for this endpoint.

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?

Very short and front-loaded, but the first two lines are redundant restatements of the same idea and the raw path adds little. It is compact without being informative.

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?

For a simple read-only list endpoint the bar is low, yet the description never says what a zone represents, whether results are tenant-scoped, or how paging behaves. It is sufficient only to guess that this lists zones.

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 100%, with top, skip and apiVersion each documented in the schema, so the baseline is 3. The description adds no meaning about paging semantics or the date-format requirement, but none is needed given full coverage.

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 only restates the name: 'Get zones / Get all zones / GET /iaas/api/zones'. It signals a list operation but never distinguishes it from the sibling iaas_get_zone (singular) or iaas_get_projects_by_id_zones, so an agent gets no discriminating detail beyond the plural.

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?

'Get all zones' weakly implies listing, but there is no statement of when to use this versus iaas_get_zone or the project-scoped zone endpoint. No prerequisites, no exclusions.

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