save_clipboard_image

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

With no annotations, the description carries the full burden. It describes saving to a PNG file, returning status and image content or error. However, it omits details about file overwriting behavior and whether the clipboard is modified.

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 well-structured with a summary sentence followed by Args and Returns sections. It is clear and concise, though the 'Args' and 'Returns' formatting adds a bit of verbosity.

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 has one parameter and returns status with image content or error. The description covers input, output, and functionality. For a simple tool, it is sufficiently complete.

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 only parameter 'output_path' is described as 'Optional output path for the PNG', which adds meaning beyond the schema's type and default. Given 0% schema coverage, this description compensates adequately.

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 tool saves an image from the macOS clipboard to a PNG file and shares it with the model. It distinguishes itself from sibling tools like 'set_clipboard_image' and 'capture_active_screen' by specifying the output format and sharing behavior.

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 explicitly state when to use this tool versus alternatives such as 'set_clipboard_image' or 'capture_active_screen'. Usage context is implied but not clearly defined.

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