screen_capture

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

No annotations are provided, so the description carries the behavioral burden. It does disclose the capture source and output quality ('native high-resolution', 'viewport framebuffer'), which implies a non-mutating operation. However, it does not describe the return format, whether optional camera parameters reposition the view, or any side effects on Studio state.

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 with no filler. It front-loads the authoritative context and communicates the essential behavior and quality in concise, specific terms.

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 tool is simple and the schema covers its optional parameters, but there is no output schema and the description does not mention what the tool returns or how the result is delivered. For an AI agent invoking this tool, the missing return-value information is a notable gap.

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 description coverage is 100%, so the schema fully documents both optional camera parameters. The description adds no parameter-level meaning beyond the schema, which is acceptable given the high coverage baseline of 3.

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 a specific verb ('Captures') and a clear resource ('Studio 3D viewport framebuffer'), and specifies important output qualities like 'clean native high-resolution'. It is readily distinguishable from all sibling tools because no other tool is described as a screenshot/capture operation.

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 does not state when this tool should be used versus alternatives, nor does it provide exclusions or conditions. 'Official Roblox Studio' gives context, but there is no guidance for an agent choosing between screen_capture and related visual or inspection tools.

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