zen_clipboard

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the basic operation and does not mention side effects (e.g., overwriting clipboard), required permissions, error handling, or what happens on invalid inputs. This is insufficient for a tool that interacts with the system.

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 extremely concise, using three lines to state the purpose and parameters. It front-loads the core function and avoids any unnecessary words or repetition.

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 tool has only two parameters and a simple function, but the description does not mention return values (e.g., clipboard content on read or success indicator on write). Given no output schema, this omission leaves the behavior partially undefined, though the operation is straightforward.

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 0% description coverage, so the description must compensate. It explains that op must be 'read' or 'write' and that text is only relevant for 'write'. This adds meaningful context beyond the schema's raw type definitions.

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 reads or writes the system clipboard using a dedicated parameter, which is a specific verb-resource pair. No sibling tools perform clipboard operations, so there is no confusion.

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 specifies the two possible values for op ('read' or 'write') and explains when text is needed, which gives implicit guidance. However, it does not explicitly state when to use this tool over alternatives or provide any broader usage context.

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