nameserver_info

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

With no annotations provided, the description carries the behavioral disclosure burden. It does state 'Read-only,' which is a meaningful safety signal, and 'one' implies a single-zone scope. However, it does not disclose authentication requirements, error behavior, or any other operational constraints.

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. The core subject is front-loaded before the read-only qualifier, making it easy to scan and quickly understand.

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 one-parameter read-only tool, the description covers the essential context: the resource type, the scope, and the read-only nature. It does not explain the output format, but no output schema exists and the tool's simplicity makes that less critical.

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 meaning by linking the 'domain' parameter to 'one INWX-hosted DNS zone,' which is useful context beyond the bare parameter name. Still, it does not specify the expected domain format or any additional constraints on the value.

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 indicates this tool returns records for a single INWX-hosted DNS zone and marks it as read-only, which clearly identifies the resource and operation type. It is reasonably distinguishable from siblings like nameserver_list, though it does not explicitly name that alternative.

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 gives no guidance on when to use this tool versus siblings such as domain_info, domain_list, or nameserver_list. The only contextual hint is 'INWX-hosted,' but there is no explicit statement of when this tool is the appropriate choice.

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