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

With no annotations, the description carries the full burden of behavioral disclosure. It does state that an AXFR attempt is made, which signals a network inspection operation, but it does not disclose side effects, failure modes, or whether the attempt could be intrusive.

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 extremely short, which is concise, but it omits essential information rather than earning its brevity. It front-loads the core idea but sacrifices parameter and usage clarity.

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 has an output schema, but the description is incomplete for an agent: it leaves the input parameter undefined, provides no usage context, and offers no annotation-backed safety or behavior hints. An agent cannot reliably determine what to pass as q.

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%, and the sole parameter 'q' has no description in the schema. The description does not explain what value q should take, such as a domain name or DNS server, making the tool nearly impossible to invoke correctly without external knowledge.

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 identifies the tool's action as an AXFR attempt and its purpose as checking whether zone transfer is misconfigured. It distinguishes itself from generic DNS siblings by naming the specific protocol and misconfiguration scenario, though it lacks a full imperative verb.

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 is provided about when to use this tool versus alternatives like dnsquery or dnsrecon. There is no mention of prerequisites, expected input context, or exclusion cases.

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