Telnet Console: Connect

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

Directly contradicts the idempotentHint: false annotation: the description twice states 'Idempotent' and explains the already-attached behavior, while the annotation declares the tool is NOT idempotent. Even though the description otherwise does an excellent job disclosing the socket-displacement side effect and the read-only caveat, the contradiction rule mandates a score of 1.

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?

Front-loaded with purpose, but the description has visible redundancy: the idempotency claim appears twice ('Idempotent: returns { connected: true, already: true }' and 'idempotent — already-attached returns { already: true }'), and the socket-displacement warning also appears twice ('connecting here will displace...' and 'displaces other clients'). The repeated claims could be merged into one sentence without losing information.

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 tool with one optional parameter, no output schema, and modest complexity, the description covers all essential operational concerns: what it does, the return value shape even without an output schema, the prerequisite for get_telnet_log, and the non-obvious side effect of displacing other socket clients. Slightly diminished by the inaccurate idempotency claim, but as a standalone description it is nearly complete.

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% — the single optional 'device' parameter already documents 'IP or serial' and the focused-tab default. The description adds no parameter detail beyond the schema, so the baseline 3 applies. No compensation needed since the schema fully covers the one parameter.

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 specific verb ('Open'), a precise resource ('BrightScript debug console TCP 8085'), and draws an exact analogy to the user clicking the Connect button. The description clearly differentiates this from siblings like telnet_disconnect, get_telnet_log, and debugger_attach by naming the port and the UI action it emulates.

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?

Provides explicit sequencing guidance: 'Lines do not accumulate until this is called' and 'After it returns successfully, poll the buffer with get_telnet_log({ afterCursor }).' This tells the agent when in a workflow this tool is required. It doesn't explicitly state exclude conditions (e.g., when to prefer debugger_attach or ECP), but for a tool with such a specific role, the context is clear and actionable.

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