dnsrecon

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

With no annotations, the description should disclose key behaviors. It only mentions 'enumeration and reconnaissance' without detailing what that entails (e.g., zone transfers, brute force, record types). No mention of destructive potential, authentication needs, 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?

The description is extremely brief but under-specified. While concise, it fails to convey essential information, making it unhelpful for tool selection and invocation.

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 no output schema, no annotations, and minimal description, the tool definition is severely incomplete. The agent cannot understand what dnsrecon returns, what actions it performs, or how to use it correctly.

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 coverage is only 33% (only dry_run described). The description adds no parameter information for 'domain' or 'session_id', failing to compensate for the low coverage. The description does not clarify their meaning or format.

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 'DNS enumeration and reconnaissance' states a broad purpose but is too generic. It does not distinguish from sibling DNS tools like subfinder or amass, which perform similar enumeration. The verb and resource are present but lacking specificity.

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 on when to use dnsrecon versus alternative tools. No when-to-use or when-not-to-use contexts are provided, leaving the agent without decision support.

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