Replace the Android clipboard content with a plain text string you provide. Clears existing clipboard data and assigns new text for use in other apps.
Replace the current clipboard with plain text.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, and the description's 'Replace' aligns with that. The description adds useful context not in annotations by specifying the new clipboard content will be 'plain text', which clarifies the tool sets plain text rather than rich content. It also implies overwriting the existing system clipboard, adding behavioral nuance beyond the structured annotations.
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, complete sentence with no filler or redundancy. Every word contributes to the tool's meaning and the core action is front-loaded. This is exemplary conciseness for a simple tool.
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 one-parameter, simple clipboard setter with no output schema, the description covers the essential operation and content type. It does not mention usage alternatives or side effects, but the simplicity of the tool and the strong annotations (destructiveHint, openWorldHint) reduce the need for extensive context. Minor gaps remain in not explicitly warning about overwriting existing clipboard content, though that's implied by 'Replace'.
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 0% description coverage, so the description must compensate. While it does not explicitly name the 'text' parameter, 'with plain text' clearly indicates that the text argument is the plain text to place on the clipboard. This conveys the parameter's purpose and type more meaningfully than the bare schema, despite not mentioning the maxLength restriction (which the schema already documents).
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 uses a specific verb ('Replace') and resource ('current clipboard') to state exactly what the tool does. It clearly distinguishes from read-only clipboard operations or share actions, though it doesn't explicitly name a sibling alternative. The scope is unambiguous enough for an agent to identify it as a clipboard setter.
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 provides no guidance on when to use this tool versus alternatives like android_clipboard_get or android_share_text. It does not mention any exclusions, prerequisites, or context that would help an agent decide between sibling tools. The intended usage is only implied by the verb 'Replace'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.