hcloud_list_dns_zones

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing further: it says nothing about result volume, pagination via the limit parameter, or what a zone listing contains. No contradiction with annotations, but no added value either.

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 only four words, so there is no waste or burying of key information. However, this brevity reflects under-specification rather than disciplined editing; there is no structure to speak of and no front-loaded detail beyond the bare action.

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 listing tool with a required region parameter and optional type/limit filters, a four-word description is thin. There is no output schema, so the description could have explained what a zone entry includes or how pagination behaves, and it omits any routing to the show/recordsets siblings.

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 three parameters (type, limit, region) are already documented in the schema, which sets the baseline at 3. The description adds no meaning beyond the schema - it does not even indicate that region is required or that type filters public vs private zones.

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?

"List DNS zones" names a verb and resource but is essentially a restatement of the tool name hcloud_list_dns_zones. It gives no scope detail (region scoping, public vs private) and does not distinguish this from the closely related siblings hcloud_show_dns_zone and hcloud_list_dns_recordsets.

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 or when-not-to-use guidance, and no mention of alternatives such as hcloud_show_dns_zone for a single zone or hcloud_list_dns_recordsets for records within a zone. The agent must infer the intended role from the name alone.

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