Type into Windows Telnet

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

The annotations already signal a non-read-only, open-world operation, and the description adds useful behavioral context: it injects real keyboard events, targets the visible session, and that text may reach the remote Telnet server. This goes beyond the annotations without contradicting them.

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 two sentences with no filler. The primary action is front-loaded, and the appendEnter behavior is stated succinctly in the second sentence.

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 simple three-parameter action with no output schema, the description covers the core behavior, the key flag, and the external transmission risk. It is mostly complete, though it could mention what happens on success or failure.

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%, so the description must compensate. It explains text as the injected payload and appendEnter as the line-submit flag, but sessionId is only implicit from its name and schema pattern. Most parameters get some semantic clarity, but not all are explicitly mapped.

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 that the tool injects text as Windows console keyboard events into a visible Telnet session, which is a specific verb and resource. It is clear in what it does, though it does not explicitly differentiate itself from the sibling tool telnet_key.

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 one concrete usage instruction: 'Set appendEnter=true to submit the line.' However, it does not explicitly say when to use this tool versus alternatives like telnet_key, nor does it mention any exclusions or prerequisites.

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