Write clipboard

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

Annotations already signal destructiveness, but the description adds crucial behavior beyond them: it overwrites the user's clipboard and does not restore it, and it tells the agent to inform the user. It also clarifies that the tool only writes the clipboard and does not perform the paste, preventing a common misuse.

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?

Three sentences, all necessary: the action, the use case, and the critical side-effect warning. The most decision-relevant facts are front-loaded, and there is no filler or repetition of schema information.

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?

For a single-parameter tool with no output schema, the description covers all an agent needs: what it does, when to use it, what it does not do, its side effects, and how it relates to sibling tools. Nothing essential is missing.

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 is 100% and the single parameter is already well described. The description adds a little extra meaning by specifying plain text and mentioning the typical use case of long or multi-line values, which helps the agent understand the character of the input beyond the schema's 'Exact text.'

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 specific verb and resource: 'Replace the system clipboard with plain text.' It also explains the intended role in a larger workflow (enabling cmd+v paste) and explicitly differentiates itself from set_value and type_text, so an agent can distinguish it from siblings without inspecting schemas.

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?

It gives concrete when-to-use context: when a long or multi-line value must be pasted via press_key and set_value is rejected or type_text would be slow. It also states a clear exclusion: 'This tool does not paste anything itself' and explicitly recommends set_value or type_text when they work.

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