wireshark_scan_file_signatures

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

Annotations declare readOnlyHint=true, and the description adds that it is an indicator (not extraction) and provides a false-positive warning. This adds context beyond the annotations, though it could detail the exact magic numbers scanned.

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?

Three sentences, front-loaded with the primary action, minimal waste. Each sentence serves a purpose: action, guidance, caution.

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?

The description covers purpose, usage, and a warning, but lacks details about the return format (e.g., count or list) and the exact set of magic numbers. For a simple tool with no output schema, it is adequate but could be more complete.

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%, but the description does not describe the 'pcap_file' parameter at all. It only implies a pcap input via context, but without explaining format, path, or expected value.

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: 'Count packets containing a file magic number', listing common magic types. It distinguishes from the sibling 'wireshark_export_objects' by noting it is an indicator, not extraction.

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?

Explicitly states when to use this tool ('indicator') and when to use an alternative ('use wireshark_export_objects to get file bytes'), and warns that hits may be coincidental.

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