Screenshot the Roblox window

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

Goes well beyond the annotations by disclosing the capture mechanism (Windows asks to draw the window directly, so nothing is raised and occluding windows don't appear), the screen-copy fallback, that the previous window is restored, and that no executor connection is required. This is consistent with readOnlyHint=true and openWorldHint=false, and it surfaces side effects (momentary window raising) that annotations do not.

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?

Front-loaded with the core action, then layered constraints and fallback details in a sensible order. Dense but each sentence carries operational content; minor tightening possible in the fallback explanation.

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 two-parameter, no-output-schema tool, the description covers platform limits, preconditions, capture path, fallback, defaults, and that the return value is an image. Nothing an agent needs to invoke it correctly appears missing.

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?

Schema coverage is already 100%, yet the description adds real meaning for 'focus' by spelling out the two behaviors (raise then restore vs. copy as-is) and the default source from config. 'max_width' is left entirely to the schema, so it is not a full 5.

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 concrete verb and resource — take a screenshot of the Roblox window and return an image — and frames the intent ("so you can see what the player sees"). It does not name or differentiate itself from the sibling 'snapshot', so an agent must infer that distinction on its own.

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?

Gives clear usage conditions: the bridge must be running on Windows, the window must be visible, not minimized and not covered. It also explains the focus flag's trade-off so the caller can choose behavior. It stops short of explicitly stating when to prefer this over 'snapshot' or 'gui_interact'.

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