get_clipboard

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

No annotations are provided, so the description must fully disclose behavior. It states the tool reads clipboard content but does not mention potential side effects (e.g., whether it modifies the clipboard), permissions needed, or error states. This is insufficient for a read operation without annotation support.

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?

A single sentence that conveys the essential purpose and details. No extraneous text, front-loaded with the verb and resource. Perfectly concise.

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?

Given no parameters and no output schema, the description covers the basic return types. However, it does not explain the format of the returned data (e.g., a string or an object with keys), nor any conditions (e.g., what happens if clipboard is empty). Slightly incomplete for full clarity.

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?

Input schema has zero parameters, so baseline is 4. The description adds no parameter details, but since there are none, it is fully adequate.

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 the verb 'reads', the resource 'clipboard content', and specifies the types of content (text, image paths, file paths). It effectively distinguishes this tool from its sibling 'set_clipboard' by indicating read vs write.

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 guidance on when to use or not, nor any mention of alternatives. The tool is straightforward, but the description lacks context like 'Use this to retrieve the current clipboard state' or exclusions. Implied usage is adequate for a simple read tool.

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