term_open

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the primary action and output, but omits important lifecycle consequences: the session persists until closed, consumes guest resources, and should be cleaned up with term_close. This makes the behavioral transparency incomplete for a stateful operation.

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, focused sentence with no filler. The core action is front-loaded, and every remaining word contributes meaning, making it highly efficient.

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?

Because there is no output schema and no annotations, the description must cover more ground. It mentions the returned session_id but does not explain how to use it with sibling tools, that sessions remain open until term_close, or any guest/SSH prerequisites. This is a meaningful gap for an agent managing an interactive session lifecycle.

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?

The description adds some parameter context: 'SSH' clarifies the transport parameter and 'real-time PTY' implies that cols and rows are terminal dimensions. However, most parameter meaning is left to the schema, and the schema's transport description is only 'Transport' while cols/rows lack semantic descriptions, so the description only partially compensates.

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 uses a specific verb ('Open'), names the resource ('real-time PTY session (SSH) on the guest'), and states a concrete return value ('session_id'). This clearly distinguishes it from sibling tools like term_close, term_send, term_read, term_exec, term_resize, and term_list, which act on an already-open session.

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 usage guidance is provided. The description does not say when to prefer term_open over term_exec, that term_open should precede term_send/term_read/term_close, or mention prerequisites such as the VM being running and SSH being available. Usage context is only weakly implied by the word 'Open'.

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