List Roblox windows

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

Annotations already declare the tool as read-only and idempotent, which covers the safety profile. The description adds the 'visible' qualifier and the 'private local' scope, which is useful behavioral context. However, it does not disclose what the tool returns (e.g., window titles, handles) or any other behavioral traits, so it only partially exceeds annotation coverage.

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 sentence that immediately states the action ('List'), the object ('visible Roblox OS windows'), and the purpose ('available for private local screenshot capture'). No wasted words; every phrase earns its place.

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?

This is a simple, low-complexity list operation with no parameters and strong annotations (read-only, idempotent). The description provides enough context to understand when and why to use the tool. Although there is no output schema, the listing purpose is adequately conveyed for an agent to proceed.

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, making schema coverage trivially 100%. The description does not need to explain parameters, and the baseline for zero-parameter tools is 4. There is no additional parameter information to add.

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 the specific verb 'List' and clearly identifies the resource: 'visible Roblox OS windows'. It also scopes the purpose to 'private local screenshot capture', which distinguishes it from sibling tools like get_tree or dump_visible_ui that inspect the UI hierarchy rather than OS-level windows.

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 phrase 'available for private local screenshot capture' implies this tool is a prerequisite for capturing screenshots, providing clear context on when to use it. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of a 5.

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