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

With no annotations to carry the safety/behavior burden, the description discloses important behavioral traits: OS-version-dependent reliability, the OS block reason, and the fact that it returns an empty-clipboard sentinel instead of a raw error. This is far beyond a generic 'read clipboard' statement.

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 main action is front-loaded, and every subsequent sentence earns its place by explaining platform constraints, failure behavior, and the recommended workaround. It is detailed without being padded.

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 description is very complete for a one-parameter tool with no annotations or output schema: it covers behavior, failure modes, and workflow. It falls just short of full completeness by not spelling out the exact successful return format or the precise sentinel value an agent should detect.

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 coverage is 100% and the single parameter udid is already described as 'Device serial number (UDID)'. The description adds no additional parameter-level detail, 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 opens with a specific verb and resource: 'Read the current clipboard content from an Android device.' It also distinguishes itself from the sibling device_clipboard_set by positioning this as the read counterpart and even references the set tool for an alternative workflow.

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 gives explicit when-to-use guidance ('Reliable on Android 12 and earlier'), when-not-to-use guidance for Android 13+, and names the exact alternative path via device_clipboard_set. No inference is required.

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