Get DNS Zone RRSet

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

Annotations already declare readonly, nondestructive, idempotent, and open-world hints. The description adds no further behavioral context (e.g., error handling, empty results, or response structure).

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?

Single sentence is concise and front-loaded with the key action. No superfluous content, but could include a brief example or note on uniqueness for improved clarity.

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 simple get operation with three well-documented parameters, the description is minimally adequate. However, it lacks guidance on distinguishing multiple results or handling non-existence, and no output schema is provided to clarify return structure.

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 coverage is 100% with descriptions for all parameters. The description merely restates parameter concepts without adding additional semantic value beyond what the schema provides.

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?

Description clearly states it retrieves a specific RRSet by zone, name, and type. The word 'specific' distinguishes it from list operations, but it doesn't explicitly contrast with sibling tools like hetzner_list_zone_rrsets.

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?

No explicit guidance on when to use this tool versus alternatives. While the 'get' verb implies a singular fetch, the description lacks context on when to prefer this over listing and filtering manually.

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