copy_selected_items

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

With only destructiveHint=false, annotations give minimal safety information. The description doesn't disclose that the operation modifies the clipboard, potentially overwriting previous clipboard contents, or whether it affects the original items (it copies, so it shouldn't). No additional behavioral context is provided.

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 a single, concise sentence with no fluff. It's appropriately short for a simple operation.

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?

Given the tool's simplicity, the description is minimal but lacks any note about the clipboard's effects or what 'selected items' means in this context. For a copy operation, it should clarify that it copies to clipboard (not duplicating in place) and that it requires existing selection.

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?

There are 0 parameters, so the schema is trivially complete. The description adds no parameter-specific information, but since none exist, a baseline of 4 is appropriate.

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 'Copy selected items to clipboard' states the verb and resource but is vague about what 'items' refers to (MIDI items, audio items, tracks?). It doesn't distinguish from sibling tools like cut_selected_items or paste_items, which are similarly named.

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. There's no mention of prerequisites (e.g., what needs to be selected) or exclusions, leaving the agent to infer that it operates on currently selected items.

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