capture

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Captures current terminal screen text' implies a read operation but does not state side effects, whether scrollback is consumed, or whether terminal state is altered. This lack of detail leaves the agent uncertain about the tool's safety profile.

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 sentence that immediately conveys the tool's core purpose. It contains no filler, repetition, or irrelevant details, making it optimally concise while still informative at a high level.

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?

The presence of an output schema reduces the need to explain return values, but the tool has two parameters and operates in a terminal context with sibling tools like scroll. The description does not explain how 'session' and 'scroll_back' affect behavior, nor whether capture requires a specific mode. With 0% schema coverage, this is insufficient for effective invocation.

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%, and the description does not mention either parameter. The required 'session' and optional 'scroll_back' remain unexplained, providing no semantic value beyond the bare names and types in the schema. The description fails to compensate for the lack of schema descriptions.

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 action ('captures') and the resource ('current terminal screen text'), providing a specific verb+resource definition. It doesn't explicitly mention sibling tools, but the action is distinct enough that no alternative is needed. Slight ambiguity in what 'capture' means (return text vs. save) prevents a 5.

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 guidance is provided on when to use capture versus scrolling or sending keys. The description does not specify whether a session must be active, whether capture works in scroll mode, or any prerequisites. It gives no context for selecting this tool over alternatives.

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