capture_fullscreen

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states only that the screen is captured but does not explain what the tool returns, whether it saves to a file, whether permission is needed, or any side effects. The optional save_path parameter hints at saving but is not described in the tool description.

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 concise sentence that directly conveys the tool's core purpose. It wastes no words and is appropriately front-loaded for a tool this simple.

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?

Given there is no output schema, annotations, or return-value information, the description is incomplete for an agent to fully understand the tool's behavior. It does not explain what happens after capture, how the save_path is used, or what the tool returns, which are essential for correct invocation.

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 input schema has full description coverage for the single optional save_path parameter, so the schema documents the parameter adequately. The tool description itself adds no parameter-level meaning beyond the schema, so a baseline of 3 is appropriate.

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 verb 'Capture' and the resource 'entire screen', which distinguishes it from siblings like capture_window and capture_region. However, it does not explicitly name alternatives or contrast itself with them beyond the scope phrase, so it falls short of a perfect 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?

There is no guidance on when to use this tool versus capture_window or capture_region. The description only implies that it is for full-screen captures, with no exclusions, conditions, or mention of alternative tools.

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