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 burden. 'Get' conveys a non-mutating read operation, but the description does not disclose error behavior, required permissions, or what is returned when the zone is not found.

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?

One short sentence with no filler; the key action, resource, and lookup key are front-loaded. It is appropriately minimal 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 and the single required parameter is fully documented, but there is no output schema and no annotation, so the description leaves return shape and failure behavior unstated. Adequate for a straightforward getter, but it relies on the agent's assumptions about 'Get'.

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%: zone_id is already documented as 'The zone ID'. The description only reinforces the 'by ID' lookup and adds no new parameter semantics 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?

States a specific verb ('Get') and resource ('DNS zone') with a precise selection criterion ('by ID'), which clearly distinguishes it from dns_zone_list and the other dns_zone_* mutations among the siblings.

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 guidance about when to use this tool versus dns_zone_list or other sibling tools. The 'by ID' phrasing implies direct retrieval when the zone_id is known, but no alternatives or when-not conditions are stated.

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