Write clipboard

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description need not repeat them. It does add the context that this uses pbcopy, which hints at execution of a system command, and that it replaces the clipboard. However, it does not add significant behavioral detail beyond that, such as potential side effects or permissions.

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 that directly states the action, the platform, and the underlying command. There is no superfluous information; it is front-loaded with the core purpose.

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 one-parameter tool with no output schema, the description covers the essential information: what it does (replace clipboard), the platform (macOS), and the command (pbcopy). It is complete enough for an agent to invoke it correctly, though it could have mentioned that it overwrites the existing clipboard, but that is implied by 'replace'.

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 input schema has 100% description coverage for the single parameter 'text' ('Text to place on the clipboard'). The description essentially restates this as 'given text', adding no additional semantic value beyond the schema.

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 action 'Replace the macOS clipboard with the given text' and explicitly mentions 'pbcopy', which is the underlying command. This distinguishes it from sibling tools like read_clipboard, making the purpose unmistakable.

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 provides clear context: it is for setting the clipboard on macOS. While it does not explicitly name alternatives or say when not to use it, the context is clear enough for an agent to understand when this tool is applicable. It does not mention exclusions, but the platform-specific hint ('macOS') implies this is not for other OSes.

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