browser_clipboard_write

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 says 'Write text to the system clipboard', which states the obvious operation but does not mention overwrite behavior, platform differences, or any side effects. The agent gains no extra insight beyond the tool's name.

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, concise sentence with no wasted words. However, it is so brief that it lacks any structured presentation of important details; it is under-specified rather than efficiently concise. It earns a 4 for being short, but not a 5 due to missing structure.

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 simple tool with one parameter and no output schema, the description is minimal. It provides the core action but omits any context about parameter expectations, clipboard behavior, or interaction with other tools. An agent could call it correctly, but it is incomplete for a robust understanding.

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 defines a single 'text' parameter with type string and zero description coverage. The tool description does not mention the parameter at all, so it adds no semantic value. Given the low schema coverage, the description should compensate, but it fails to do so.

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 states a clear verb ('Write') and resource ('text to the system clipboard'), and implicitly distinguishes from sibling tools like browser_clipboard_write_image by specifying 'text'. It is not a tautology because it adds the 'text' qualifier, but it is minimal and does not elaborate on any specifics.

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 given on when to use this tool versus alternatives. There is no mention of conditions, prerequisites, or references to sibling clipboard tools. The agent is left without any routing cues.

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