capture_screen

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

With no annotations, the description carries the full behavioral burden. It hints that output shape depends on mode ('buffer display in buffer mode, cleaned stream otherwise'), but never confirms this is a read-only, non-mutating operation, nor describes session prerequisites, error behavior, or how include_ansi interacts with the two output modes.

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?

A single front-loaded sentence with a parenthetical qualifier; no filler or repetition. It is efficient, though the brevity is partly under-specification rather than disciplined conciseness.

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?

An output schema exists, so return values need not be explained, but for a zero-annotation, zero-parameter-documentation tool the description is too thin. It leaves mode selection, session targeting, and interaction of include_ansi with the output modes unaddressed.

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% across all 3 parameters, so the description must compensate. 'Buffer mode' loosely maps to use_buffer and 'cleaned stream' loosely to include_ansi, but session_id is never mentioned and the default/null semantics of use_buffer are unexplained.

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 and resource ('Capture the current screen') and the parenthetical clarifies what the capture yields. It implicitly separates this from line/region siblings like get_line and get_screen_region by scoping to the whole screen, though it never names them.

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?

There is no explicit guidance on when to prefer this over get_screen_region, get_line, or get_cursor_position, nor any stated preconditions (e.g., an active session). The agent must infer usage purely from the tool name.

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