hcloud_get_zone_rrset

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

Annotations already cover readOnly/openWorld/destructive, so the description's added value is the primary-mode precondition and the concrete 422 `incorrect_zone_mode` failure mode, which an agent cannot get from annotations. It stops short of describing return shape or lookup semantics, but the disclosed constraint is meaningful context.

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?

Front-loaded with the verb+resource and the key mode restriction within the first three short lines. The error table adds formatting weight but only one row is relevant, so there is minor bloat.

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?

A three-required-param read tool with no output schema is mostly adequately described, and the mode caveat covers the main failure mode. It still doesn't indicate what identifiers resolve against (id_or_name scope) or what the returned RRSet contains, which would matter for an agent consuming the result.

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%, including the non-trivial rr_name casing/Punycode/apex rules and the rr_type enum, so the schema does all the parameter work. The description adds no parameter-level meaning beyond that, which is the expected baseline.

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+resource ("Get an RRSet") and clarifies it returns a single RRSet from a Zone, which implicitly separates it from the list sibling hcloud_get_zone_rrsets. Sibling differentiation is implied by "single" rather than stated explicitly, so it falls just 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?

"Only applicable for Zones in primary mode" is a real usage constraint and the only conditional guidance present. However, it does not name what to do otherwise (e.g., use zonefile/records endpoints or the plural list tool), leaving the agent to infer the alternative path.

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