List DNS zones

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

The readOnlyHint annotation already covers safety, and the description adds that the response includes status, mode, TTL, nameservers, and record counts. However, it does not disclose details about pagination behavior, rate limits, or how filters interact, which would be useful context.

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 a single sentence, front-loaded with the action and resource, and contains no unnecessary words. It efficiently conveys the purpose and key output details.

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 list operation with good schema coverage and readOnly annotation, the description is complete enough. It explains what the tool returns, and the schema covers filtering and pagination parameters. It doesn't mention default pagination or total count, but those are minor gaps.

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%, so all five parameters are well-documented in the schema. The description adds no additional parameter-specific meaning beyond what the schema provides, so a score of 3 is appropriate as the baseline.

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 the tool lists DNS zones of the Hetzner Cloud project, using the specific verb 'List' and resource 'DNS zones'. It also specifies included attributes (status, mode, TTL, nameservers, record counts), which distinguishes it from single-zone retrieval tools like get_zone.

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 by stating it lists zones, but does not explicitly mention when to use this tool over alternatives such as get_zone or export_zonefile. It also lacks guidance on filtering or pagination, though those details are present in the schema.

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