zyxel_connect

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention that a persistent session is created, that the tool might overwrite an existing connection, or any side effects like timeouts or authentication failures. This is insufficient transparency for a connection tool.

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, clear sentence with no unnecessary words. It is appropriately front-loaded and concise, conveying the essential purpose efficiently.

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 7 parameters and no output schema, the description provides only the most basic context. It does not explain the connection lifecycle, such as whether the session persists across commands, how to manage multiple connections, or what happens on failure. This leaves gaps for an AI agent to infer.

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 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides. It does not explain the relationship between protocol and port defaults or the purpose of enablePassword, thus adding no extra semantic value.

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 resource 'Zyxel switch' with the methods 'Telnet or SSH'. This distinguishes the tool from siblings like zyxel_disconnect, zyxel_connection_status, and various configuration commands, which are clearly different operations.

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 implies usage as a preliminary step before other Zyxel commands, but it does not explicitly state when to use it or when not to. No guidance is given on prerequisites, alternative connection methods, or that a connection must be established before other tools will work.

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