tcpvcon

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

With no annotations, the description carries the full behavioral burden. It discloses that it wraps a Sysinternals binary and parses CSV output, which hints at the mechanism, but it omits whether elevated privileges are required, whether enumeration is system-wide, and any side effects. "List" implies a safe read, but that is inference rather than disclosure.

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?

Purpose is front-loaded in one line, followed by a compact implementation note and a return-shape block. Slightly redundant given a formal output schema already exists, but nothing is bloated.

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 single-parameter read tool with an output schema present, the definition covers purpose, mechanism, and return format adequately. The remaining gap is the absence of any privilege or environment requirement, which would matter for a tool that wraps an admin-level Sysinternals utility.

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 100%, and the single all_states parameter is documented in the schema with its -a flag and default. The description adds no further parameter meaning beyond what the schema already states, so the baseline 3 applies.

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?

Specific verb ("List") plus specific resource ("TCP/UDP connections") plus scope ("with owning process"), and it identifies the underlying implementation (Sysinternals Tcpvcon). No sibling tool in the list covers network connections, so the agent can route to it unambiguously.

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 statement of when to use this tool versus anything else, no preconditions, and no exclusions. It presumes the agent already knows it wants a connection listing; nothing in the text helps it decide.

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