list_dns_zones

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

The annotations already disclose readOnlyHint=true, and the description does not contradict that. The operation described is simply a listing, with no additional side effects or restrictions mentioned. With annotations providing the key behavioral trait, the description adds limited extra value beyond what the annotations already convey.

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, concise sentence in Russian that states the operation, the resource, and the environment. It also embeds the API endpoint reference. Every word earns its place, and no unnecessary details are included.

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?

The tool has a low complexity profile: no parameters, no output schema, and a read-only operation. The description specifies exactly what the tool does (returns all DNS zones of the account) and the context (PowerDNS Hostkey). Annotations already provide the safety profile, so nothing further is necessary to enable correct invocation.

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 has zero parameters, so the schema provides 100% coverage by definition. Since there are no inputs to describe, the description cannot add parameter meaning; the baseline for 0 parameters is 4.

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 uses the specific verb 'list' and the resource 'DNS zones' (Список всех DNS-зон), and states the account scope. The presence of the underlying API call 'pdns/list_zones' adds a clear reference that distinguishes it from sibling tools like list_dns_domains or get_dns_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 explicitly says it lists all DNS zones of the account, making the primary use case evident. However, it provides no explicit guidance about when to choose this tool over related alternatives (e.g., get_dns_zone for a single zone), leaving usage implied rather than directly stated.

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