clear_scrollback

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the action (clearing scrollback) and a prerequisite but does not disclose side effects, irreversibility, impact on other sessions, or performance implications. The description is minimal and leaves important behavioral aspects unaddressed.

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: two sentences totaling 16 words. The first sentence front-loads the primary action, and the second sentence adds necessary prerequisite. No wasted words.

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 it is a simple tool with one parameter and no output schema, the description covers the basic action and prerequisite. However, it omits details like irreversibility, confirmation of success, or error conditions. It is minimally complete for the tool's simplicity but has room for improvement.

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 adds context that 'session_id' must be from a session created via create_session(session_id, cwd). This gives meaning beyond the bare schema, but it does not explain the format or constraints of session_id. The addition is helpful but incomplete.

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 tool's purpose: 'Clear rendered scrollback history while preserving current screen.' This is a specific verb ('Clear') and resource ('rendered scrollback history'), and it distinguishes itself from sibling tools like snapshot_scrollback (which retrieves scrollback) and snapshot_screen (which captures screen).

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 mentions a prerequisite ('Requires an existing session created via create_session(session_id, cwd)') but provides no guidance on when to use this tool versus alternatives. For example, it does not contrast with snapshot_scrollback (for reading scrollback) or send_control (which might clear the screen). No when-not-to-use information is given.

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