snapshot_screen

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

With no annotations, the description provides important context: it is a 'passive snapshot' and 'does not ingest new PTY bytes'. This clarifies it's a read-only operation without 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?

Three sentences: main action, prerequisite, behavioral note. No unnecessary 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?

Covers purpose, prerequisite, and behavior. Lacks information about the return format (e.g., plain text or structured data), but since there is no output schema, this is a minor gap.

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 0%, so description must compensate. It explains that `session_id` must belong to an existing session from `create_session`, adding context beyond the schema's title and required flag. But no format or validation details.

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 verb 'Get' and resource 'current VT100-rendered terminal screen snapshot'. It distinguishes from siblings like `snapshot_scrollback` by specifying 'screen' vs scrollback.

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?

Explicitly requires an existing session via `create_session(session_id, cwd)`. However, does not explicitly compare with siblings like `snapshot_scrollback` or `transcript`.

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