apple_clipboard

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'Read and write' but does not disclose that 'set' and 'clear' are destructive operations, nor that protected actions may require confirmation (hinted by the 'confirm' parameter). This is minimal transparency.

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 sentence that front-loads the core purpose and then lists the actions. Every word contributes value, with no redundancy or extraneous detail, making it appropriately sized for the tool's simplicity.

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 tool is simple and the schema covers parameters well, but with no annotations or output schema, the description leaves gaps: it does not specify what 'get' returns, nor the confirmation requirement for destructive actions. While adequate for a basic tool, it could be more complete given the absence of structured safety hints.

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 provides thorough descriptions for all three parameters, including the meaning of each enum value. The description only repeats 'get, set, clear' without adding new syntax, format details, or edge-case behavior, so the baseline of 3 for high schema coverage 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 'Read and write the macOS clipboard' and lists the specific actions 'get, set, clear.' This is a specific verb+resource that distinguishes it from sibling tools like apple_system or apple_finder, which handle different system features.

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 that the tool is for macOS clipboard interactions, and the listed actions imply when each operation would be used. It does not explicitly name alternatives or exclusions, but given the tool's unique scope, the context is sufficient for an agent to select it appropriately.

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