rba_capture_roblox_screenshot

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

With no annotations provided, the description carries the full burden. It does disclose the primary behavior (capturing the process) and the return type (MCP image). However, it omits behavioral details such as whether the window is brought to foreground, how failures are handled (e.g., process not found), and whether the capture is of the full screen or just the window. The mention of 'for visual context' adds a small hint about purpose but not deeper 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, well-structured sentence that front-loads the action and target, then states the output. No wasted words or redundant information. It is appropriately sized 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?

The description covers the core purpose and return value, and the schema handles parameters. However, it lacks explicit usage context (when to choose this over similar tools), potential failure scenarios, and any prerequisites. Given the absence of an output schema and annotations, the description is minimally viable but not comprehensive.

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 schema has 100% description coverage for its three optional parameters, so the baseline is 3. The description adds no additional semantics beyond what the schema already provides, such as the role of 'outputPath' or 'focusWindow'. It does not reference or clarify any parameter usage, so it does not exceed the baseline.

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 the action ('Capture') and the specific target ('RobloxPlayerBeta.exe'), and distinguishes it from the sibling tool 'rba_capture_window_screenshot' by focusing on the Roblox process. The output ('screenshot as an MCP image') is also explicit, making the purpose unambiguous.

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?

Usage is implied by the mention of RobloxPlayerBeta.exe: the tool is for capturing the Roblox game window. However, there is no explicit guidance on when to prefer this over the general 'rba_capture_window_screenshot' sibling, nor any exclusion conditions (e.g., when Roblox is not running).

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