clipboard

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

Description states the tool can write to clipboard, but annotation idempotentHint=true implies the operation is safe to retry without side effects. Writing is typically not idempotent, creating a contradiction. The description adds 'activates the tab first' but is undermined by the inconsistency.

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 a single, efficient sentence that conveys the core purpose and a key behavior (tab activation). No redundant or unnecessary words.

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 does not mention return values for read operations or error handling. With no output schema, the user is left uninformed about what the tool returns on read. The tab_id parameter behavior is explained in schema but not reinforced in description.

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 100%, so the baseline is 3. The description does not add any additional meaning beyond what the schema already provides for the three parameters.

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 verb 'read or write' and the resource 'system clipboard (text)', and adds a specific behavioral detail 'activates the tab first'. It uniquely identifies the tool among siblings, as no other sibling tool mentions clipboard operations.

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 explicit guidance on when to use this tool versus alternatives. The description implies clipboard interaction but does not mention when-not or suggest alternative tools for similar tasks (e.g., using type_text for paste).

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