Reflect: Get Screenshot

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the active-session precondition and the 'current state' nature of the capture, which is useful, but it does not disclose behavior such as what happens when no active session exists or how the screenshot is returned.

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 front-loaded with a clear one-sentence purpose, followed by a compact toolset label and parameter list. It is appropriately short, though the parameter list mostly duplicates the input schema.

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 read-only tool with only two parameters, the description is largely adequate. However, there is no output schema, and the description does not clarify the return format of the screenshot (e.g., binary, base64, URL), nor does it explicitly state the connection prerequisite. This is a meaningful but not severe 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 100%, giving a baseline of 3. The description adds value by qualifying the session as active and placing the screenshot in the current state context, which is not fully captured by the schema's simple 'The ID of the Reflect recording session' description.

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 uses a specific verb and object: 'Capture a screenshot from the current state of an active Reflect recording session.' It clearly identifies the resource (Reflect recording session) and distinguishes this operation from sibling Reflect tools that list segments, execute suites, or manage tests.

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 implies when to use the tool by mentioning an 'active Reflect recording session,' but it does not explicitly state prerequisites, such as connecting to a session first, nor does it provide when-not-to-use guidance or alternatives. It is adequate context but relies on inference.

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