save_capture_to_file

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

Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds little beyond 'capture network traffic'. It fails to disclose that capturing requires network interface access, may require root privileges, or that it writes to the filesystem. Major behavioral gaps remain.

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 short but somewhat redundant with the schema. The parameter list adds value but could be more concise by omitting obvious repetitions. Adequate but not tightly written.

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 5 parameters, no output schema, and basic annotations, the description lacks information about return values, error conditions (e.g., permission denied, file exists), and execution context (e.g., blocks for duration). Significant gaps for a network capture tool that writes files.

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 0%, so description must compensate but only provides one-line descriptions that essentially repeat parameter names (e.g., 'Network interface name'). It does not explain formatting for 'bpf_filter', or that 'duration' and 'packet_count' have defaults. Insufficient for a 5-parameter tool.

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 verb 'capture', resource 'network traffic', and output 'save to a PCAP file'. It distinguishes itself from siblings like 'capture_live_packets' by explicitly mentioning persistent storage.

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 says 'Useful when you want to keep a capture for later analysis,' which implies when to use but does not provide explicit when-not-to-use or alternatives. Guidance is implied rather than explicit.

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