terminal.type

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

With no annotations, the description carries the full burden but only discloses that it types text without appending Enter. It omits details such as whether the text appears instantly, how special characters are handled, or if the tool blocks until the typing is complete. More behavioral context is needed.

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 extremely concise with two sentences, no unnecessary information, and the key behavior is front-loaded. Every word earns its place.

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 the complexity of terminal interactions and the lack of output schema, the description is too minimal. It does not explain how this tool fits with other session tools, whether it returns any result, or how to handle errors (e.g., invalid sessionId). More context is needed for reliable agent use.

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% with clear parameter descriptions. The description adds the behavioral note about Enter not being appended, which relates to the text parameter. However, this does not significantly enhance meaning beyond the schema, so a 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 ('Type text') and the target resource ('terminal session'), and adds a key specificity: 'Does not append Enter automatically'. This distinguishes it from sibling tools like terminal.paste or terminal.press.

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 when you need to type text into a terminal session, and the hint about Enter helps with expectation, but it does not explicitly state when to use this tool vs. alternatives (e.g., paste for larger blocks, press for special keys) or mention prerequisites like session activity.

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