clipboard

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully discloses the 90-second timeout and the mutating write mode, but it does not mention side effects of overwriting clipboard contents or any platform-specific restrictions.

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?

Two short sentences, front-loaded with the core operation and a single high-value timeout constraint. Every sentence earns its place and there is no filler or 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?

For a straightforward read/write tool with an output schema and a well-covered parameter schema, the description captures the essential behavior and timeout. It could clarify that write expects text, but the schema and enums already cover most of the context.

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 89%, so the baseline is 3. The description only hints at the text parameter with 'given text' and restates the action modes, adding little meaning beyond what the schema already documents.

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 pairs two distinct verbs, 'Read' and 'replace', with a specific resource ('device clipboard text') and explicitly covers both action enum values. An agent can tell exactly what the tool does without opening the schema, and it is clearly distinct from sibling tools like type or click.

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 intended use for read vs write is obvious, but there is no explicit guidance about when to prefer this tool over alternatives or any exclusions. The agent must infer that read is for retrieving clipboard content and write is for setting it.

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