Tcpdump Probe

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

With no annotations, the description carries the burden of behavioral disclosure. It adds the prerequisite 'requires privileged_tools' and the 'short' scope, but does not explain capture behavior, duration, filters, permission implications, or output.

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?

One compact sentence with the core scope and prerequisite front-loaded. No filler, though the brevity comes at the cost of missing details.

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?

For a low-level packet capture tool, the description omits important operational context such as capture length, count, interface/filter options, and how results are returned. The trivial schema and lack of annotations leave the agent without enough to invoke it robustly.

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 schema is a bare wrapper around an unstructured params object, so the description's reference to host:port is the only meaningful parameter guidance. However, it does not specify the expected object shape (e.g., separate host/port keys vs. a single host:port string).

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 identifies the tool as a short tcpdump capture targeting host:port, which is a specific verb and resource. It is distinguishable from most siblings, though it does not explicitly name an alternative.

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 tcpdump_probe versus network-related siblings like tcp_connect, tcp_connect_as, or linux_network. The only context provided is the privileged_tools prerequisite, not a use-case or exclusion.

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