cloak_screenshot

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

Without annotations, the description must disclose behavioral traits. It only states the basic function and output format, omitting crucial details like whether the screenshot captures the full page or viewport, any side effects, or prerequisites. The optional parameters 'question' and 'annotate' are not explained in terms of their impact on 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 extremely concise with two short sentences, no redundancy, and front-loaded information. Every word earns its place, efficiently conveying the primary action and output.

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 the tool's complexity with two optional parameters and no output schema, the description is inadequate. It fails to explain the purpose of the 'question' parameter or how 'annotate' alters the screenshot. The return value is stated as PNG, but details about image dimensions or behavior under different page states are missing, leaving significant gaps.

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 baseline is 3. The description adds no additional meaning beyond the schema. While the schema sufficiently describes the parameters, the description does not clarify how 'question' interacts with the screenshot or why 'annotate' might be used, missing an opportunity to enhance understanding.

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 ('take a screenshot') and the resource ('current page'), and specifies the output format (PNG). However, it does not differentiate from siblings like 'cloak_snapshot', which might also capture visual state, lacking specificity about the exact nature of this screenshot tool.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of which scenario is appropriate for screenshotting vs. using other tools like cloak_snapshot or cloak_get_content, leaving the agent without decision-making context.

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