System Set Clipboard

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

Annotations are present but the description adds no behavioral context beyond them. It does not mention that clipboard content is replaced, whether accessibility or automation permissions are required, or any side effects.

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 short, but its only sentence is boilerplate that does not earn its place. It provides no functional information and is under-specified rather than concisely complete.

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 has an output schema, but the description still fails to state the actual action or any practical context. An agent can infer the operation from the name and text parameter, but the description itself is not complete enough.

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 0% and the description does not explain the 'text' parameter or its role. The description adds no semantic value beyond what the input schema already shows.

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 merely restates the tool name as a 'Delegated Apple domain tool' and says it is exposed through Apple-Tools-MCP. It does not state that the tool sets the system clipboard, beyond what the name/title already imply.

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 provided about when to use this tool or when to prefer an alternative. Siblings such as system_get_clipboard exist, but the description does not distinguish this tool from them.

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