set_clipboard

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

Annotations are all false, so they don't convey behavioral traits. The description adds valuable information: macOS-only (uses pbcopy), which implies platform restrictions and dependency. It also clearly indicates a write operation. No contradictions with annotations.

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 two sentences, front-loaded with the primary action, followed by the platform restriction and a concrete use case. There is no fluff; every word contributes meaning.

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 one-parameter clipboard write with no output schema, the description covers the essential context: what it does, platform limitations, and when to use it. No missing information that would hinder correct invocation.

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 already fully describes the single parameter 'text' with 'Text to place on the clipboard.' The description adds no additional detail about format, length, or encoding, so it is exactly at the baseline for full schema coverage.

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 uses the specific verb 'Write' with the resource 'system clipboard', clearly stating the tool's function. The macOS-only note and pbcopy dependency further distinguish it from the sibling get_clipboard, which performs the inverse operation.

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 explicit usage context: 'Use to copy a result or command output so the user can paste it anywhere.' This makes the intended scenario clear, though it does not explicitly contrast with get_clipboard or mention any exclusions. Still, it gives strong practical guidance.

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