retrieve_dns_zone

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the endpoint path and the fact that all attributes are returned, but says nothing about behavior on a nonexistent zone or about permission requirements — acceptable given the annotation coverage, but not enriching.

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?

Two short lines, zero waste, with the identifying scope (by zone name) front-loaded before the secondary 'get all attributes' clause. Nothing padding and nothing buried.

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 one-required-parameter read with full annotation coverage this is close to adequate, but with no output schema the description could say what the zone object contains or how a missing zone is signalled. It leaves the agent to infer error semantics.

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% for both parameters, so the schema already documents zoneName and x-trace-id. The description's phrase 'by zone name' reinforces the required parameter but adds no format, case-sensitivity, or rate-limit detail beyond the schema.

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 states a specific verb and resource: retrieve a single DNS Zone identified by zone name, returning all its attributes. This is distinguishable from the sibling retrieve_dns_zones_list (plural collection) and create/delete_dns_zone, though it never explicitly names those alternatives.

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?

'Retrieve a DNS Zone by zone name' plus 'Get all attributes for a specific DNS Zone' implies the single-record read case, but the description never states when to prefer it over retrieve_dns_zones_list or retrieve_dns_zone_records_list. Usage is inferable from naming rather than stated.

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