Read or write Windows clipboard

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

Annotations already indicate this is not a read-only tool, and the description accurately reflects read/write behavior without contradicting annotations. However, beyond the basic dual-action behavior, it does not disclose details such as what happens on a non-text clipboard, whether setting overwrites existing content, or possible failure modes.

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, compact sentence that is front-loaded with the tool's purpose. There is no filler or redundant restatement of the tool name.

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 simple two-parameter clipboard tool, the description is minimally adequate, but it leaves gaps: it does not specify the return behavior for `get`, nor the dependency between `action=set` and the `text` field. The lack of an output schema makes these omissions more noticeable.

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 0%, so the description needed to compensate by explaining how `action` and `text` relate. Instead, it merely restates 'read text' and 'write text' without mapping those actions to the get/set enum or clarifying that `text` is needed for the set action. The schema provides names and enum values but no semantic guidance.

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 tool's function with specific verbs 'read' and 'write' plus the resource 'Windows clipboard' in the title and description. It is immediately distinguishable from sibling tools like read_file, write_file, and computer_input.

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 communicates the core use case but provides no explicit guidance on when to prefer this tool over alternatives or when not to use it. Usage context is implied by the 'interactive Windows clipboard' phrasing, but no exclusions or alternative tool references are given.

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