retrieve_dns_zones_list

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is fully covered. The description adds nothing beyond the HTTP path — no mention of pagination behavior, default page size, or whether results are scoped to a tenant/customer.

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 second sentence ("Get a list of all zones") simply restates the first, and the bracketed path duplicates the endpoint already implied. Slight redundancy rather than tight economy.

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?

Adequate for a simple read-only list tool with full schema coverage and rich annotations, but it omits pagination expectations and the fact that filtering is available, which an agent would need to call it well.

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% across all 7 params, so the schema carries the semantics; the description adds no additional meaning about filters, ordering syntax, or trace headers. Baseline 3 applies.

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?

States a specific verb and resource ("List DNS zones", GET /v1/dns/zones) and clearly reads as a collection endpoint. The singular sibling retrieve_dns_zone is implicitly distinguished by the plural, though the description never says so explicitly.

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 on when to use this versus retrieve_dns_zone or retrieve_dns_zone_records_list, and no note that filters (zoneName, customerId, tenantId) are optional narrowing. The agent must infer usage entirely from the name.

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