clipboard_set

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

With no annotations provided, the description carries full transparency burden. It states the basic action but omits critical behavioral details: what happens if both 'text' and 'image_b64' are provided, whether they are mutually exclusive, size limits (though schema has maxLength for text), and error behavior. The absence of these disclosures leaves ambiguity for the agent.

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, focused sentence that communicates the core function without any wasted words. It is appropriately sized for a simple tool and immediately front-loads the purpose.

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 setter, the description covers the essential function, but gaps remain: no mention of mutual exclusivity or precedence of parameters, no handling of empty input, and no note about whether the operation is synchronous or has side effects. These missing edge cases make it adequate but not fully 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?

The schema covers 0% of parameter descriptions, so the description must compensate. It successfully maps 'text' to text content and 'image_b64' to a base64 PNG, and the word 'or' implies mutual exclusivity. However, it doesn't explain constraints (e.g., max length, encoding requirements) or clarify what happens if neither parameter is provided.

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 ('Set') and resource ('the clipboard'), clearly distinguishing it from siblings like clipboard_get and clipboard_paste. It also enumerates the two supported content types (text, base64 PNG), making the tool's scope unmistakable.

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 implies when to use the tool (any time you want to set clipboard content) but offers no explicit guidance on alternatives, exclusions, or when to choose text versus image. It relies on the obviousness of the operation rather than providing directional advice.

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