Copy text to the host clipboard (sUNC setclipboard / toclipboard)

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

Rich disclosure beyond annotations: the overwrite of existing clipboard contents, the fallback function, the type-guard/pcall wrapping, exact error object and return shape, and required preconditions. However it declares 'idempotency=idempotent-write' while the annotations set idempotentHint=false, a direct conflict on a retry-relevant trait that an agent could act on.

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?

Front-loaded with the critical fact ('WRITES HOST STATE') and the overwrite warning, which is good. But it is bloated with metadata tags (Phase, cost, idempotency, Produces) and a redundant signature dump, plus a trailing 'On failure: inspect tool-schema...' sentence that is filler.

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?

With no output schema, the description compensates by specifying the return shape ({ ok, length } or { error }), the exact failure object, prerequisites, and a verification tool. An agent has everything needed to invoke and check the call.

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 100% and all three parameters are documented in the schema; the description merely restates the signature, adding no new meaning. Baseline 3 is appropriate when the schema carries the semantics.

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 ('copies the given text to the host machine's OS clipboard') and even names the underlying primitives (setclipboard/toclipboard). No sibling tool touches the clipboard, so it is trivially distinguishable from the rest of the catalog.

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?

Gives clear preconditions (requires an available setclipboard/toclipboard, active-client, explicit-mutation-approval) and a follow-up (verify with assert-state). It does not name a when-not or an alternative tool, but no plausible alternative exists, so context is sufficient.

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