ui_clipboard_write

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

The description adds valuable context beyond annotations: it mentions execution on an STA thread via FlaUI bridge, and full Unicode support including emoji and CJK. Annotations only provide openWorldHint: false, offering no behavioral detail.

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 concise: three sentences plus an args section. It is front-loaded with the purpose, followed by technical detail, and then parameter documentation. No unnecessary 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 write tool with one parameter and no output schema, the description covers purpose, technical constraints, and input format. However, it lacks information about return value or error conditions, which would improve completeness.

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 description repeats the parameter name 'text' with a minimal explanation ('The text to write to the clipboard'), adding little beyond the schema. While it mentions Unicode support, it does not specify length limits or special encoding requirements.

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 explicitly states 'Write text to the system clipboard', using a specific verb and resource. It clearly distinguishes from sibling tool ui_clipboard_read which reads clipboard content.

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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternatives like ui_clipboard_read. However, the purpose is self-evident, so it remains adequate.

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