snapshot_2d

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

With no annotations, the description carries the full burden. 'Capture' implies an action but does not disclose what the tool does precisely (e.g., returns an image, saves a file, or just copies to clipboard), nor any side effects or requirements. The description is too terse to adequately inform the agent about behavior.

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, concise sentence that is appropriately front-loaded. It conveys the core action and context without any fluff. Perfectly efficient for the tool's simplicity.

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 tool with no parameters and no output schema, the description still fails to explain the result of the snapshot (e.g., where it is stored, what format, or how to retrieve it). Additionally, it does not clarify how this differs from the sibling 'snapshot' tool, leaving a potential gap in tool selection.

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?

The tool has zero parameters, so the schema already covers all parameter semantics trivially. The description adds no parameter-specific information, but none is needed. Baseline 4 applies per the rubric for 0-parameter tools.

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 states a specific verb ('Capture') and resource ('the 2D pattern window') and adds context ('pattern pieces layout'). It is clear and matches the tool name, but it does not explicitly differentiate from the sibling 'snapshot' tool, which may have a similar purpose.

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 on when to use this tool versus alternatives. It does not mention conditions, prerequisites, or contrasts with other capture tools like 'snapshot' or 'clo_ui_screenshot'. The agent is left to infer usage from the name alone.

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