clipboard

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

With no annotations, the description carries the full burden. It discloses that non-text content returns empty string on read and that write overwrites clipboard. It lacks information on permissions or side effects beyond overwriting, but is largely 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?

Three sentences, front-loaded with key information, no wasted words. Every sentence serves a purpose: purpose, semantics, caveats.

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?

The description explains read and write behavior but does not cover return values for write, and the 'include' parameter is only in schema. Given no output schema, more detail on outputs would be beneficial. The tool is relatively simple, so completeness is adequate but not perfect.

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 input schema has descriptions for all parameters (action, text, include). The description adds meaning for action but does not elaborate on 'include'. Since schema coverage is high, baseline is 3 and the description does not significantly add beyond schema.

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 it reads or writes the Windows clipboard, specifying the resource and actions. It distinguishes between two modes and includes caveats, making its purpose unambiguous.

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 explains when to use each action (read vs write) and what they do. However, it does not mention when not to use this tool or provide alternatives, though none are obvious among siblings.

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