get_clipboard

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

No annotations provided, so the description carries the full burden. It does not mention that it operates on a simulator device, whether an empty clipboard returns an error or null, permissions, or what the returned content looks like. 'Get' implies a safe read but this is not stated.

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?

One short, front-loaded sentence with no waste. However, it is arguably too terse for a tool with no annotations and no usage guidance, so it's conciseness at the expense of completeness.

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?

An output schema exists, so return-value explanation is not needed. But with no annotations, no usage guidance, and no behavioral context (error handling on empty clipboard, device scoping), the description is minimal-viable rather than complete for a simulator tool.

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% (device_id fully documented as Simulator UDID), so baseline 3 applies. The description adds no parameter-level detail beyond what the schema provides.

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?

States a specific verb (get) and resource (clipboard/pasteboard content), clearly distinguishing it from set_clipboard. The only gap is the lack of explicit statement that this reads from a simulator device, though the device_id param implies it.

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 explicit when-to-use guidance or alternatives named. Given the sibling set includes set_clipboard as the obvious counterpart, the description could have said 'reads clipboard content; to write, use set_clipboard'. Implied usage only.

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