Write the Android clipboard

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive, open-world), so the description's real contribution is the runtime dependency on the termux-api package and app, which is genuine behavioral context an agent needs before calling. It stops short of describing failure behavior when the dependency is missing.

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 short sentences, zero waste, with the action front-loaded and the prerequisite following. Nothing repeats structured data.

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 write with a complete schema and full annotation coverage, the description supplies the critical missing piece (the Termux:API dependency) and nothing more is needed since there is no output schema. Minor gap: no mention of what happens if the dependency is absent.

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 coverage is 100% and the single 'text' parameter is fully documented in the schema, so the description does not need to restate it. Baseline 3 applies since the description adds no meaning beyond the schema.

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?

States a specific verb and resource ('Set the Android clipboard text') plus the mechanism (Termux:API), making it immediately distinguishable from the clipboard_get sibling. It falls just short of a 5 because it doesn't explicitly frame itself against that sibling or state any scope limits.

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 prerequisites ('termux-api package and Termux:API app') imply when the call will succeed, but there is no guidance on when to prefer this over alternatives such as run_command or termux_api, nor any exclusions. Usage is implied rather than stated.

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