disable_dns_resolution

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

No annotations provided, and the description only mentions disabling DNS resolution without explaining behavioral implications such as speed impact or limitation to IP addresses. The meaning of 'scan' is vague.

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 concise with a front-loaded sentence and a structured Args/Returns format. However, the Returns section is minimal and could be integrated into the main description.

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?

Without output schema, annotations, or detailed parameter info, the description lacks completeness. It does not explain the structure of the returned dictionary or edge cases.

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 0%, so the description must compensate. It notes target as IP/hostname and args as Nmap arguments, which adds basic meaning, but does not specify format or constraints for args (e.g., allowed flags).

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 it performs a scan with DNS resolution disabled, which is a specific verb-resource pair. It distinguishes from siblings that do not disable DNS resolution, though it does not specify the type of scan (e.g., port scan, host discovery).

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 this tool versus alternatives like syn_scan or ping_scan. The description does not mention scenarios where disabling DNS resolution is beneficial or necessary.

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