read_clipboard

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the tool's safety profile. The description adds only the word 'current' to indicate it reads the present clipboard state, but it does not disclose potential failure modes, permissions, or return format. It is consistent with annotations, so no contradiction, but it adds little beyond them.

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 a single concise sentence that front-loads the key information. Every word earns its place; there is no redundancy or filler.

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 zero-argument read operation with strong annotations and no output schema, the description is fully sufficient. The expected return (clipboard text) is implied by the verb and resource, and no additional context is needed for an agent to invoke it correctly.

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?

The tool has zero parameters and an empty input schema, so there is nothing for the description to explain. Per the rubric, a 0-parameter tool gets a baseline of 4, and the description correctly makes no parameter claims.

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 'Read the current clipboard text' uses a specific verb ('Read') and a specific resource ('current clipboard text'), clearly distinguishing it from siblings like write_clipboard and clear_clipboard even without naming them. The intent is unambiguous and cannot be confused with any other tool in the list.

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 implies the tool should be used when the clipboard's text content is needed, but it provides no explicit guidance about when to use it versus write_clipboard or clear_clipboard. There are no exclusions or alternative recommendations, so the usage context is only implied.

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