copy_to_clipboard

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 the action but does not mention potential side effects (e.g., overwriting clipboard contents), prerequisites (e.g., image must be loaded), or error behavior. The description is adequate but minimal for a simple operation.

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, direct sentence with zero excess words. It is front-loaded with the action and resource, making it immediately scannable. Perfect conciseness for a tool of this simplicity.

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 simplicity, one parameter, and the presence of an output schema (which likely describes return values), the description is mostly sufficient. However, it omits any contextual cues about when to use it (e.g., for pasting into external apps) and lacks explicit behavioral details. It is adequate but not thorough.

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 coverage for the single parameter is 100% (the schema already describes image_id as 'ID of the image to copy'). The description adds no additional meaning beyond what the schema provides, so it meets the baseline expectation but does not exceed it.

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 uses a specific verb ('Copy') and specific resource ('an image to the system clipboard'), making the tool's purpose unmistakable. It clearly distinguishes itself from sibling tools like save_image or open_in_preview by naming the destination (clipboard) rather than file or preview.

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_image or open_in_preview. There is no mention of scenarios where copying to clipboard is preferred, nor any exclusions. An agent must infer when this is appropriate.

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