save_screenshot

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 only states the action without mentioning file naming behavior, destination folder semantics, overwrite behavior, permissions, or any side effects beyond saving a screenshot. This is minimal disclosure for a tool that creates a file.

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 clear sentence with no wasted words, and the primary action is front-loaded. It is appropriately short for a simple tool, though the brevity leaves important behavioral and parameter information unaddressed.

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, has no required parameters, and an output schema exists, so the description is minimally usable for basic invocation. However, with no annotation coverage and no parameter explanations, it is not fully complete for an agent deciding how to customize the screenshot or interpret the side effect.

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 0%, and the description adds no meaning to the two parameters beyond what their names and defaults already suggest. An agent cannot learn from the description what 'folder' affects or how 'name' should be formatted.

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 states a clear verb and resource: 'Save a screenshot of the current page.' It is unambiguous about what the tool does and is distinct from page-source or PDF saving in intent, though it does not explicitly differentiate itself from sibling tools like save_page_source or save_as_pdf.

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 gives no guidance on when to use this tool versus alternatives such as save_page_source or save_as_pdf. It implies the use case through the name and phrasing, but excludes no contexts and names no alternatives.

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