Focus visible Telnet window

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

The description adds behavioral context beyond the annotations: it clarifies that the tool affects the real conhost.exe window and brings it to the foreground, and annotations indicate it is neither read-only nor destructive. However, it does not mention side effects such as stealing focus, potential failure conditions, or whether it can reveal a minimized or hidden window.

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 clear, front-loaded sentence with no filler. It communicates the operation and target 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?

For a very simple tool with one parameter and no output schema, the purpose is stated clearly enough to attempt a call. Still, the description lacks usage conditions, parameter mapping, and behavioral side effects, so it is only minimally 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 description coverage is 0%, and the description does not mention sessionId or explain how it identifies the target Telnet session. The parameter name and UUID format make the meaning partially inferable, but the description itself provides no compensating semantic guidance.

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 exactly what the tool does: 'Restores and brings the real conhost.exe Telnet window to the foreground.' This distinguishes it clearly from sibling tools like telnet_start, telnet_close, and telnet_read by targeting window focus rather than session lifecycle or I/O.

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?

No explicit guidance is given about when to use this tool versus alternatives, when it is appropriate, or what prerequisites exist (e.g., the session must already be started and its window must exist). The usage context must be inferred entirely from the tool name and sibling list.

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