Clears the staged (unexecuted) command line in an iTerm2 session, equivalent to pressing Ctrl-U, to discard a proposed command before execution.
Clear the staged (unexecuted) command line in a session (Ctrl-U).
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | No | Session ID from list_iterm_sessions. Optional: defaults to the last session used. |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It clarifies that the command is unexecuted and therefore not running, but it does not state reversibility, what happens when nothing is staged, or any session side effects.
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?
One sentence, front-loaded with the action and target. The parenthetical clarification and Ctrl-U shortcut both add useful information without waste.
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 tool with one fully documented optional parameter and no output schema, the description covers the action, target, and shortcut adequately. It has a minor gap around edge-case behavior such as clearing when no command is staged.
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 100%; the sole session_id parameter is fully documented in the schema, including its optional default. The description adds no additional parameter meaning beyond the schema.
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, resource, and scope: 'Clear the staged (unexecuted) command line in a session.' The parenthetical 'unexecuted' implicitly distinguishes it from execute_command, so an agent can tell what it does without opening the schema.
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 phrase 'staged (unexecuted) command line' gives clear context for when to use it: to discard a proposed command before execution. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.