dns_zone_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get records for a zone' and does not explain what kind of records are returned, whether all zones/domains are covered, error behavior, authentication needs, or any other behavioral detail. It is accurate but extremely thin.

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 two short sentences with no filler. It front-loads the core purpose and then defines the only parameter. Every word earns its place for a single-parameter read tool.

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?

The tool is simple with one required parameter and an output schema exists, so the description is nearly sufficient to make a correct call. Still, there is no usage context, no clarification of scope, and no mention of how this relates to other DNS tools, leaving some gaps for an agent.

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 0%, so the description must compensate. It adds the meaning 'Zone name' to the 'domain' parameter, which is slightly more specific than the schema's bare 'Domain' title. However, it provides no format, example, or qualification such as whether a trailing dot is expected, so the compensation is minimal.

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 clear verb and resource: 'Get records for a zone.' This makes the tool's purpose immediately understandable and distinct from mutation tools like dns_record_add and dns_record_delete. It does not explicitly differentiate from sibling read/DNS tools such as dns_admin_list, so it stops 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 guidance on when to use this tool versus alternatives. The description does not mention related DNS tools, prerequisites, or exclusions, so an agent receives no help deciding between this and other DNS endpoints.

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