hijack_dangling_ns

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

With no annotations, the description must explain behavior. It explains the detection mechanism (NS hostname resolving to NXDOMAIN) and the security impact, but does not mention return format, edge cases, or whether it is read-only. It adds context but leaves some behavioral gaps.

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, with the action front-loaded in the first sentence and the security context in the second. Every sentence contributes meaning without redundancy.

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 description adequately explains what the tool does and why it matters, but without an output schema it does not describe the return format or result structure. For a simple one-parameter detector, this is a notable omission.

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?

The input schema already fully documents the single 'domain' parameter with an example. The description adds no extra parameter-level detail, so it earns the baseline 3 for full schema coverage.

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 purpose: detecting dangling NS records that could lead to full domain takeover. It uses specific language ('Detect dangling NS records') and the vulnerability explanation distinguishes it from sibling tools like hijack_dangling_cname and hijack_dangling_mx.

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: it is for detecting NS-specific dangling records. However, it does not explicitly mention alternatives or when not to use it (e.g., for CNAME records), so it stops short of a full when/when-not distinction.

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