screen_capture

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

With no annotations provided, the description carries the full disclosure burden. It usefully reveals the return type ('as an image') for a tool with no output schema, but says nothing about capture resolution, image format, which window wins when 'Studio' and 'active screen' differ, or failure behavior when the window is absent.

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?

A single front-loaded sentence that leads with the verb and result. It is efficient, though the hedged phrase '2021 Roblox Studio / Aisaka window or active screen' adds clutter without resolving the ambiguity it introduces.

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 zero-parameter tool with no output schema and no annotations, the description covers the essentials: what is captured and that an image is returned. The only real gap is which capture target is selected when multiple windows exist, which an agent may need to know.

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 takes zero parameters, so there is no parameter semantics to document and the description has nothing to compensate for. Baseline 4 applies per the zero-parameter rule.

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?

States a specific verb ('Captures') and resource ('screenshot'), and the output ('returns it as an image'), which clearly separates it from siblings like get_tree or execute_luau. The qualifier '2021 Roblox Studio / Aisaka window or active screen' is oddly specific and leaves the exact capture target ambiguous, so it stops short of 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?

'for visual inspection' implies the intent behind the tool, giving minimal but real usage context. It never states when to prefer this over alternatives such as get_tree or get_output_log, nor any conditions or prerequisites, so guidance is only implied rather than explicit.

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