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

With no annotations present, the description carries the full behavioral burden. It does disclose a meaningful operational constraint ('Requires an active iOS automation session'), which is useful context. However, it does not mention side effects, failure modes, or whether the operation overwrites existing pasteboard content beyond what is obvious from 'Set.'

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 short sentences with no filler. The core action is front-loaded, and the operational prerequisite is stated efficiently.

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 two-parameter setter with full schema coverage, the description is mostly adequate: it states what it does and the required session. The main gap is failing to clarify how this tool relates to the sibling ios_clipboard_set_hid, which could lead an agent to pick the wrong clipboard method.

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 100%, so the schema already documents 'udid' and 'content' fully. The description adds no parameter-level meaning beyond what the input schema provides, so the baseline score of 3 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 a specific action ('Set the clipboard/pasteboard content') and targets a specific resource (an iOS device). It distinguishes itself from read-style siblings like ios_get_pasteboard and device_clipboard_get, but it does not differentiate from similar setters such as ios_clipboard_set_hid or device_clipboard_set.

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 a prerequisite ('Requires an active iOS automation session') but gives no guidance on when to choose this tool over closely related alternatives like ios_clipboard_set_hid or device_clipboard_set. There is no mention of exclusions or criteria for selecting the non-HID vs HID clipboard setter.

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