screenshot

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It states the tool captures and returns a PNG, but it fails to detail what area is captured (full window, specific region), whether any side effects occur, or if it works in all application states. This is insufficient for a tool with zero annotations.

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, clear sentence with no unnecessary words. It efficiently captures the essential purpose and output format.

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?

Given the tool has no parameters and is straightforward, the description is mostly complete. However, it lacks details about the exact screen area captured and any potential size or resolution considerations. The absence of an output schema is not fully compensated.

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?

There are no parameters, and the schema coverage is 100%. The description does not need to add parameter information, but it could have explained any implicit inputs. According to the rubric, zero parameters baseline is 4, and the description meets this standard.

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 that the tool captures the current screen of OrcaSlicer and returns a PNG image. The verb 'capture' and resource 'OrcaSlicer screen' are specific, and the output format is explicitly defined, distinguishing it from sibling tools like click, export_gcode, etc.

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 usage when a screenshot is needed, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or constraints. The context is clear but lacks exclusions or when-not-to-use advice.

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