hcloud_show_dns_zone

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. The description adds nothing beyond that: it does not say what "details" comprise (recordsets? nameservers? status?), whether the call fails for private zones, or what the region scoping implies. With no output schema, that omission matters.

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 or redundancy. It is efficient, though its brevity borders on under-specification rather than tight scoping.

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 detail-retrieval tool with no output schema, three parameters, and an enum distinguishing public from private zones, the description leaves out what is returned and any behavioral edge cases. An agent can call it, but cannot predict the response shape or failure modes from the definition.

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 all three parameters (region, zone_id, zone_type) are documented in the schema including the enum for zone_type, so the baseline of 3 applies. The description contributes no additional meaning, such as whether zone_type must match the zone's actual type or whether region is required for 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?

The description uses a specific verb ("Get details") on a specific resource ("a specific DNS zone"), which is enough for an agent to distinguish it from the plural sibling hcloud_list_dns_zones. It does not explicitly name that sibling or state the singular/listing contrast, keeping it short of a 5.

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 statement of when to use this instead of hcloud_list_dns_zones or hcloud_list_dns_recordsets, and no prerequisites or exclusions are given. The agent must infer from the name alone that this is the single-zone detail call.

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