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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds useful context by listing the fields returned (TTL, answers, filter chain, linked record, region settings), but does not disclose any behavioral traits beyond annotations such as error handling, auth requirements, or rate limits.

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 sentences with zero waste: the first front-loads the purpose and enumerates return fields, the second gives the exact HTTP endpoint. Every element is informative and appropriately sized for a simple getter.

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 read-only, single-record GET tool with full schema coverage and safety annotations, the description is complete: it identifies the resource, lists key return fields (compensating for the lack of an output schema), and provides the underlying endpoint. No critical operational detail is missing.

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%, so all three parameters (zone, domain, type) are already fully documented in the schema. The description simply restates that the record is identified by zone, domain, and type, adding no additional meaning or format details 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?

The description clearly states the specific resource ('one DNS record') and the three scoping parameters (zone, domain, type), and lists the returned fields. It implicitly distinguishes itself from list operations with 'One', but does not explicitly name a sibling alternative for contrast.

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?

The description provides no when-to-use guidance, no alternatives, and no conditions under which this tool should be preferred over sibling tools like ns1_list_zones or ns1_get_zone. Usage is only inferable from the required parameters and the endpoint.

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