paste_image

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

No annotations are provided, so the description carries full responsibility. It discloses the key behavioral traits: captures clipboard data, saves to a temporary file, and returns the file path. This adds meaningful transparency, though it does not cover edge cases like an empty clipboard or file cleanup.

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 compact and front-loaded with the primary action. It consists of two sentences that efficiently convey the operation, behavior, and supported formats, with no wasted words.

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 with no output schema, but the description explains the return value (file path) and the save-to-file behavior. It lacks details about prerequisites (e.g., clipboard must contain an image) and potential failure modes, which would make it more complete. Still, for a straightforward clipboard utility, it covers sufficient context.

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?

Both parameters are fully described in the input schema, so the description does not need to add much. The description mentions support for common image formats, which aligns with the format enum, but adds no additional syntax or format details beyond what the schema already provides. Baseline of 3 is appropriate since schema coverage is 100%.

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's function: pasting an image from the system clipboard, saving it to a temporary file, and returning the file path. It distinguishes paste_image from sibling tools (enable_auto_paste, disable_auto_paste, auto_paste_status) which manage auto-paste settings rather than directly pasting an image.

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 clearly implies when to use this tool: when an image is in the clipboard and needs to be displayed via Claude Code. It doesn't explicitly name alternatives or exclusions, but the sibling tools are clearly about toggling auto-paste, so the context is unambiguous. This is a clear usage context without explicit when-not guidance.

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