clipboard_set

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

No annotations are provided, so the description carries the burden. It states the core action (setting clipboard text) but does not disclose prerequisites, side effects, or failure conditions. It is adequate but lacks behavioral depth.

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 two short sentences, front-loaded with the primary action and followed by a practical tip. Every word earns its place with no redundancy.

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 simplicity of the operation and the existence of an output schema, the description covers the essential purpose and a key usage pattern. It doesn't mention device prerequisites or edge cases, but for a clipboard setter it is reasonably 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?

Schema coverage is 0%, so the description must compensate. The wording 'clipboard text' maps to the 'text' parameter and 'on the device' maps to 'device', giving basic semantic meaning. However, it does not explain valid formats, constraints, or how to obtain a device identifier.

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 a specific action: 'Set clipboard text on the device.' It identifies the verb 'set', the resource 'clipboard text', and the scope 'device', distinguishing it from sibling tools like clipboard_get (read) and type_text (direct input).

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 provides an explicit usage context: 'Use with press_key(PASTE) to paste into fields.' This tells the agent a common workflow, though it does not explicitly mention alternatives or when not to use the tool.

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