wireshark_extract_dhcp_info

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

The description states it returns 'DHCP lease information or JSON error', implying a read-only operation. However, without annotations, it could be improved by explicitly noting it does not modify the file or require special permissions.

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 clear structure: tag, summary, args, returns, example. Every sentence adds value, and it is front-loaded with the key purpose.

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?

Given the tool's simplicity and the presence of an output schema, the description is complete enough for selecting and invoking the tool. It could mention prerequisites (e.g., valid pcap file) but is otherwise adequate.

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?

Only one parameter (pcap_file) is described as 'Path to capture file', adding meaning beyond the schema's title. With 0% schema description coverage, the description compensates effectively for the single param but does not detail file format constraints.

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 extracts DHCP lease information, listing specific data types (IPs, hostnames, DNS servers, lease times). This distinguishes it from sibling tools like extract_dns_queries or extract_credentials, providing a specific verb and resource.

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 guidance on when to use this tool vs alternatives. Among many sibling tools, there is no context about when DHCP extraction is appropriate or when other tools might be preferred.

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