tunnel_txt_payload

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

No annotations are provided, so the description carries the full burden. It discloses the process (resolve TXT records, detect payloads) and specifies the detection heuristics (base64, hex, binary markers, high-entropy). While it does not mention side effects or output format, it clearly indicates a read-only analysis behavior, which is more transparent than typical tool descriptions.

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 a single, information-dense sentence that front-loads the core action and scope. It does not waste words and covers all key aspects: resolving records, subdomains, and detection types.

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 provides a full understanding of what the tool does and what types of detections to expect. It covers all parameters and the overall process. The lack of an output schema is not a major gap because the purpose is clear, though explicitly describing the return value would improve completeness.

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 100% with descriptive parameter names and descriptions. The tool description adds no additional parameter semantics beyond what the schema already provides; it merely repeats 'domain' and 'optional subdomains' without offering syntax or edge-case details.

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 uses a specific verb ('Resolves') with a clear object ('TXT records') and a distinct purpose ('detects encoded payloads commonly used in DNS tunneling'). It explicitly enumerates detection types (base64, hex, binary markers, high-entropy content), which distinguishes it from sibling tools like tunnel_query_length or tunnel_entropy_analysis.

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 when to use the tool—when investigating DNS tunneling via TXT records—but it does not explicitly state alternatives or exclusion conditions. There is no comparison with sibling tunnel analysis tools, so an agent must infer the context from the domain-specific wording.

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