hcloud_get_zone_zonefile

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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds real value beyond them: what is actually produced (a generated BIND-format zone file), the primary-mode restriction, and the specific failure mode with its HTTP status and error code. No mention of size limits or download mechanics, but the behavioral core is covered.

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 core behavior and format are front-loaded in the first two sentences, and the mode restriction follows. The error table plus inline markdown anchor/link syntax adds some noise but each block carries distinct, useful information.

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?

With no output schema, the description compensates by naming the return value and its format, and it documents the one realistic failure condition. For a single-parameter read operation this is close to fully sufficient; only download/encoding details are absent.

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%, and the single parameter id_or_name is fully described in the schema as "ID or Name of the Zone." The description adds nothing about the parameter, so the 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 ("Export a Zone file") and specifies the exact output format (BIND RFC 1034/1035). It is clearly distinct from the inverse sibling hcloud_zone_import_zonefile_action, though it never names it 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?

Gives a hard precondition: "Only applicable for Zones in primary mode," reinforced by the 422 incorrect_zone_mode error row. It doesn't name an alternative tool for secondary-mode zones, but the applicability constraint is explicit and actionable.

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