List Tcp6

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it says nothing: not whether the operation is read-only, what it returns, whether it requires elevation, or how results are scoped or ordered. For a tool with zero annotation coverage this is a complete behavioral gap.

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 single short sentence is front-loaded but not concise in a useful sense; it is under-specified rather than tight. There is no structure beyond a bare noun phrase and no qualifier that earns its place.

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?

Because an output schema exists, return values need not be explained, and there are no parameters. The remaining gap is the total absence of selection guidance against the many sibling list/find/get tools, which an agent needs in order to choose this one correctly.

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 there is no parameter semantics to document and the schema is trivially complete. The baseline of 4 applies with no compensating detail needed in the description.

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?

States a verb ('列出' / list) and a resource (IPv6 TCP), so the basic purpose is conveyed. However, it does not clarify what aspect of IPv6 TCP is listed (connections, ports, listeners) nor explicitly contrast itself with list_tcp, list_tcp4, or list_udp6, leaving the scope somewhat vague.

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 gives no indication of when to use this tool versus list_tcp, list_tcp4, or the get_* / find_* siblings. There is only an implied IPv6/TCP filter from the name, with no conditions, prerequisites, or alternatives stated.

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