Tcp Connect As

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

No annotations are provided, so the description carries the full disclosure burden. It mentions the privileged_tools permission requirement but discloses nothing else: no side effects, failure behavior, or network probe implications. It does not even state whether the operation is read-only, unlike the more explicit tcp_connect sibling.

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?

A single front-loaded sentence conveys the core purpose efficiently with no filler. However, it is written in Russian while sibling descriptions appear English, which may reduce scannability for some agents, and it is arguably terse to the point of omission.

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 0% schema coverage, no annotations, and an open params object, the description is far too thin. The output schema exists but the input contract is entirely unspecified. An agent cannot reliably construct a valid call because the filter and identity parameters are never documented.

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 coverage is 0% and the sole parameter is an open 'params' anyOf object with additionalProperties:true — effectively undocumented. The description hints at 'per-uid filters' as the semantic content but gives no format, required fields, or example, leaving the agent to guess what the service-user identity and filters look like.

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 states a specific verb and resource: a TCP probe executed as a service user with per-uid filters, plus a privilege requirement. This is clear and implies differentiation from the sibling tcp_connect ('as a service user'), though it never names the sibling explicitly.

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 only usage guidance is a prerequisite — 'requires privileged_tools'. There is no stated when-to-use vs the sibling tcp_connect, no exclusions, and no indication of what scenario selects this tool over the apparently simpler tcp_connect.

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