infra_software_cve

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal the query method (CHAOS version.bind TXT) and outcomes (identifies versions, maps to CVEs), but it does not disclose limitations such as failure when version.bind is disabled, output format, or potential rate-limit considerations.

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?

Two concise sentences, front-loaded with the core action. Every word adds value, and there is no redundant information or filler.

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?

For a single-parameter tool with a clear schema and no output schema, the description covers purpose, method, and target software scope. It could be more complete by noting CHAOS query limitations or expected result shape, but it is sufficiently informative for an AI agent to invoke it appropriately.

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%, so the baseline is 3. The description only restates the parameter's purpose ('DNS nameserver to fingerprint') without adding format details, constraints, or edge-case guidance beyond what the schema already provides.

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 states a specific verb and resource: 'Fingerprint DNS server software via CHAOS class version.bind TXT query and map to known CVEs.' It also lists the targeted software (BIND, PowerDNS, Unbound, NSD, Knot DNS), which clearly distinguishes it from the sibling tool dns_server_fingerprint by adding CVE mapping.

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 explicit when-to-use or alternative guidance is provided. However, the description strongly implies usage for DNS software fingerprinting and CVE association. It does not mention the overlapping sibling tool dns_server_fingerprint or when to prefer one over the other.

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