paste_clipboard

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

With no annotations, the description carries the behavioral disclosure burden. It reveals the underlying clipboard command, clarifies this tool copies rather than pastes, and explains how type_text routes non-ASCII text automatically. It could mention side effects or failure modes, but for a clipboard-copy operation this is reasonably transparent.

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 concise and front-loaded with the core purpose, then provides relevant usage guidance in two short follow-up sentences. Every sentence adds useful information without filler.

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 simple clipboard tool, the description covers purpose, usage timing, and the key alternative sibling. The main gap is the unexplained 'serial' parameter, but since it is optional and an output schema exists, the description is otherwise sufficient.

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%, so the description must compensate. It implicitly explains the 'text' parameter by stating the tool copies text, but the optional 'serial' parameter is never mentioned or explained. With one parameter semantically opaque, the description only partially compensates for the missing schema descriptions.

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 copies text to the device clipboard and even names the underlying command ('cmd clipboard set-primary-clip'). It also distinguishes itself from type_text by explaining when each is appropriate.

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 explicitly says to prefer type_text for accented/unicode text and to use this tool when you only want to copy without immediately pasting, or when you need to paste the same text multiple times. This is clear, actionable usage guidance.

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