clipboard

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

The description discloses that write overwrites the clipboard and that this is not recoverable, which is critical behavioral information beyond the annotations. It also notes that the tab is activated first, adding transparency about side effects.

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 exceptionally concise, consisting of two short sentences that pack essential information without anyone. The structure is logical, starting with the core function and then adding the warning.

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 covers the primary function and the critical warning, but lacks guidance on alternative tools or edge cases (e.g., what happens when reading an empty clipboard). Given the absence of an output schema, a bit more context about expected behavior would improve completeness.

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 descriptions already fully explain all parameters (action, text, tab_id) with 100% coverage. The tool description does not add extra semantic meaning beyond the schema, so a baseline of 3 is appropriate.

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 (text), which is a specific verb and resource. It also clarifies the scope to text, leaving no ambiguity about the tool's function.

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 does not mention when to use this tool versus alternatives like type_text or read_page. It only mentions 'Activates the tab first' as an operational note, but provides no guidance on appropriate use cases or conditions where another tool would be more suitable.

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