sec.connections

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

With no annotations, the description carries the full burden, and it discloses almost nothing: it does not say whether the call is read-only (implied but unstated), whether elevated privileges are required to resolve PID/process ownership (a real constraint for socket-to-process mapping), or anything about output shape or snapshot semantics.

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?

It is a single sentence with no padding, which is good, but the compactness comes from omission rather than discipline. The most decision-relevant fact, contrast with sec.listening, is missing entirely.

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 zero-param tool with no annotations and no output schema, the description must supply the missing context itself. It does not explain the privilege requirement, the returned fields, or how it differs from the many sibling network/security tools, so it is not sufficient to invoke confidently.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed, and there is nothing further the schema could or should document.

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 names the resource ('active sockets') and the returned columns ('owning PID/process'), which is informative. But it is a noun phrase with no verb and gives no differentiation from the adjacent sibling sec.listening, so an agent cannot tell from the text alone which of the two returns established/active connections versus listening ports.

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?

There is no guidance on when to call this versus sec.listening, sec.exposure, or net.portscan. The description gives no context, prerequisites, or exclusions, leaving the agent to infer usage from 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.