get_capture_file_info

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

The annotations (readOnlyHint, destructiveHint, idempotentHint) already declare this as a safe, read-only operation. The description adds no behavioral details beyond the annotation set, such as file existence expectations or error handling, which is acceptable but not additive.

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 extremely concise at two lines, with no wasted words. It is front-loaded with the purpose. However, it could benefit from a brief example or note on supported paths without becoming verbose.

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 no output schema, the description should explain what metadata is returned (e.g., file size, packet count). It does not, leaving the agent unsure of the output shape. The tool is simple but still incomplete in this regard.

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?

The single parameter 'filepath' has no description in the schema (0% coverage). The description adds 'Path to PCAP/PCAPNG file', clarifying accepted file types. This provides minimal additional meaning beyond the schema's type and title.

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 'Get' and the resource 'metadata about a PCAP capture file'. It differentiates from the similarly named 'get_capture_info' by specifying 'file', implying a single file operation. However, it could be more precise about what metadata is included.

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 is provided on when to use this tool versus alternatives like 'get_capture_info' or other analysis tools. The description gives no context for selection, leaving the agent to infer based on the tool name alone.

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