analyze_network_connections

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

With no annotations, the description must disclose behavioral traits, but it only mentions high-level analysis and outputs. It does not state whether the tool requires special permissions, performs active scanning, or has side effects like writing to the output file.

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 compact and front-loaded, with two sentences of purpose followed by a concise parameter list. Every sentence contributes value with no redundancy.

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 presence of an output schema covers return values, but the description lacks operational context such as permission requirements, potential network impact, and the meaning of 'suspicious connections.' The tool is moderately complex, so more context would help.

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 description adds meaning with an Args section, explaining device_id as an optional device serial number and output_file as a path to save JSON results. This goes beyond the bare schema titles, though it omits any detailed constraints or interactions.

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 analyzes active network connections and configuration, listing specific outputs like connected networks, open ports, and suspicious connections. This differentiates it from sibling tools focused on logs, processes, or packages.

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 implies use for network analysis but provides no explicit guidance on when to prefer this tool over alternatives, nor any exclusions or prerequisites. It is not misleading but leaves the agent to infer the context.

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