clipboard_set

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

The description discloses an important behavioral side effect: 'VM remains locked by this session; call vm_unlock when finished.' This goes beyond the annotations (which only indicate readOnlyHint false) by informing the agent about the lock state and required follow-up action.

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?

Two sentences, each serving a distinct purpose: the first states the action, the second provides the critical lock/unlock instruction. No wasted words.

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 one-parameter setter, the description covers the action, the target environment (Windows 98), and the session lock behavior that requires vm_unlock. It lacks an explicit return value, but none is needed for a setter.

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 schema has one parameter 'text' with no description. The tool description implies the parameter is the replacement clipboard text, but does not explicitly explain its format or any constraints. Since schema coverage is 0%, the description partially compensates by associating 'text' with clipboard text, but could be clearer.

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: 'Replace Windows 98 clipboard text.' This is a specific verb+resource and distinguishes clipboard_set from clipboard_get and other input tools.

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?

Provides a clear context: the VM remains locked by this session and instructs to call vm_unlock when finished. However, it does not explicitly mention alternatives or when not to use it, so it's slightly below a perfect score.

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