clipboard

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

The description lacks any behavioral details. It does not disclose that writing overwrites the device clipboard, that the tool requires an active device session, or that device parameters are needed. With no annotations, the description carries the full burden and fails.

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 at 6 words, but it sacrifices informativeness. It could be slightly expanded without becoming verbose.

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?

With 23 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain device selection, output format for read, or that the tool manipulates a remote device clipboard.

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?

Despite high schema coverage (91%), the description adds no additional meaning beyond the schema. The critical 'action' and 'text' parameters are not explained in the tool description—e.g., that 'text' is required when action is 'write'.

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 clipboard text, with a specific verb and resource. No sibling tool duplicates this functionality, so it is distinct.

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?

No guidance is provided on when to use this tool versus alternatives, when to choose read versus write, or any prerequisites such as device connection.

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