get_network_connections

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

No annotations are provided, so the description bears full responsibility. It fails to disclose behavioral traits such as whether the operation is read-only, requires elevated privileges, or has performance implications. The description only states what is returned, not how the tool behaves.

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 concise (one sentence plus a fragment) but poorly structured. The fragment after the period ('protocol: tcp, udp, both, all.') reads as an afterthought. While brevity is valued, some organization would improve clarity.

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 the lack of output schema, annotations, and low schema coverage, the description is inadequate. It does not specify the output format, fields returned (e.g., local/remote addresses, state), or error conditions. For a tool with this complexity and many siblings, the description fails to provide enough context for reliable invocation.

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%, yet the description only adds meaning to the 'protocol' parameter (listing valid values). The 'process_name' and 'pid' parameters are completely undocumented, leaving the agent guessing their purpose and format. The description does not compensate for the schema gap.

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 retrieves 'TCP and/or UDP endpoints with owning process', specifying a verb ('get') and a resource ('network connections'). It also enumerates protocol values (tcp, udp, both, all), making the purpose reasonably clear. However, it does not differentiate from sibling tools like 'get_process_details' or 'list_processes'.

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 explicit guidance is given on when to use this tool versus alternatives. The description does not mention prerequisites, limitations, or context for invocation. Agents have no basis to choose this over sibling tools.

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