dns_zone_transfer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the network protocol (TCP), the action (AXFR attempt), the outcome if successful ('all DNS records in the zone are returned'), and the security significance. However, it does not explain what happens when the transfer is refused (e.g., error or empty response), leaving some behavioral ambiguity.

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 sentences, front-loaded with the action and followed by impact. Every word earns its place, with no redundancy or irrelevant details.

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?

Given the tool's simplicity (2 parameters, no output schema), the description covers its purpose, method, and outcome. It briefly describes return content ('all DNS records') but lacks explicit failure-mode behavior, which would make it fully complete 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 100% for both parameters, with clear descriptions for 'domain' and 'nameserver'. The tool description adds minimal extra semantic value beyond the schema, so the baseline of 3 is appropriate.

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 tool's action: 'Attempt an AXFR (full zone transfer) against a domain's nameserver via TCP.' This specific verb and resource clearly distinguish it from other DNS tools like dns_lookup or infra_axfr_protection, which have different purposes.

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 clear context that this is a security assessment tool by stating 'An open zone transfer is a critical security misconfiguration.' It implies when to use it (to check for misconfigured nameservers) but does not explicitly mention alternatives or when-not-to-use cases, which prevents a perfect score.

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