hijack_ns_delegation

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

With no annotations, the description carries the full burden. It discloses the checks performed (lame delegation, glue, NS mismatch) which indicates a read-only verification behavior. However, it does not mention output format, permissions needed, or whether it performs live DNS queries. This is adequate but incomplete for a tool with no annotation support.

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 core action, and every clause adds specific value. It avoids fluff and repetition, making it efficient for an AI agent to parse.

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 has no output schema, so the description must convey return behavior. It lists the checks but does not state whether the tool returns a boolean, a list of issues, or a report. For a verification tool, this is a notable gap. However, the complexity is moderate (single parameter, specific checks), so the description is partially complete.

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 the single 'domain' parameter, which is already clearly documented. The tool description adds no additional param semantics beyond restating that the domain is the focus. Baseline 3 is appropriate since the schema does the heavy lifting.

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 a specific action: 'Walk the DNS delegation chain and verify consistency.' It enumerates concrete checks (lame delegation, missing glue records, NS mismatch) that distinguish it from sibling tools like dns_zone_transfer or hijack_dangling_ns. The verb+resource+scope are specific and unambiguous.

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 implies usage context: when you need to verify DNS delegation integrity. However, it does not explicitly compare to alternatives or state when not to use it. With siblings like hijack_dangling_ns and dnssec_check_ds, some exclusion guidance would help, but the context is clear enough for an informed agent.

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