zyxel_connect

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. It does not explain what happens after connecting (e.g., whether a persistent session is held), whether the tool blocks or times out, or what state changes occur on the switch. For a connection tool, this is a significant 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 description is a single concise sentence with no redundancy. It efficiently communicates the core purpose and protocol. However, it is too brief to convey behavioral context, but conciseness itself is well-executed.

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?

With 7 parameters, no output schema, and no annotations, the description is inadequate. It does not mention what the tool returns (e.g., session handle or status), whether it must be called once before other commands, or any side effects. This is a complex operational tool that needs more context than a single sentence.

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%, ensuring every parameter is documented in the schema. The tool description adds no parameter information beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 action ('Connect') and the target resource ('Zyxel switch'), and specifies the protocols ('Telnet or SSH'). This distinguishes it from sibling tools that perform show/config operations. It is specific but does not mention what connection state is established or that it should precede other commands.

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 use this tool relative to alternatives. It does not state that connection must be established before using other zyxel tools, nor does it describe prerequisites like network reachability or authentication setup. The sibling tools like zyxel_disconnect and zyxel_connection_status imply a usage flow, but the description lacks this context.

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