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

While annotations cover technical safety (readOnlyHint: true), the description adds critical behavioral context about the data itself ('Clipboard contents may be sensitive') and ethical guidelines ('do not send them to unrelated sites').

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 definition is concise and perfectly structured: first, it states the functional purpose, and second, it immediately follows up with crucial safety and behavioral constraints. Both sentences are necessary.

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 (one parameter) and highly annotated. The description provides all necessary context regarding the tool's purpose, safety profile, and appropriate usage, leaving no ambiguity for the agent.

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%. The parameter `device` is fully detailed in the input schema itself. Therefore, the description adds no meaningful semantic value beyond the required baseline when structured data is complete.

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 defines the function ('inspect the current clipboard text') and the domain ('on a paired computer'). Given the extensive sibling list, this is highly specific and distinguishes it from write or clear operations.

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?

It provides a perfect trigger condition ('when the user asks to inspect the current clipboard text'). Crucially, it also provides strong usage restrictions regarding data sensitivity and when to use it ('read them only when needed').

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