list_dns_zones

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-reach profile are covered. The description adds only modest extra context: 'all' zones for the whole account (i.e., no filtering) and the backing service (PowerDNS Hostkey servers). It says nothing about pagination, result volume, or ordering, which is the main behavioral gap for a bulk list call.

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?

A single front-loaded sentence with no filler that maps directly onto the tool name and the underlying API method. It is docked slightly because the text is stored in a corrupted encoding (Cyrillic rendered as mojibake), which costs an agent readability even though the sentence itself is tight.

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 read-only, zero-parameter list tool with no output schema, the description covers the essentials (what is listed, for which account, from which backend). It omits anything about result shape or whether the full zone set is returned in one call, which is the remaining useful detail given there is no output schema to fall back on.

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 tool takes zero parameters, so per the rubric the baseline is 4; there is no syntax or format detail the description could usefully add. Schema coverage is 100% (empty object), so nothing is left undocumented.

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 (mojibake-decoded: 'List of all account DNS zones on PowerDNS Hostkey servers (pdns/list_zones)') gives a specific verb ('list'), resource ('DNS zones'), and an explicit backend scope that separates it from generic listing tools. It does not, however, explicitly distinguish itself from close siblings such as list_dns_domains, list_dns_subdomains, or get_dns_zone, so the agent must infer the boundary.

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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives, despite four very similar DNS-listing siblings in the toolset. The agent is told only what the tool returns, not the condition that should select it over list_dns_domains or get_dns_zone.

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