pattern_clone

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

No annotations provided, so description carries full burden. It only mentions copying notes and grid bits but omits side effects like whether mixer routing, color, or selections are cloned. Does not state if a new pattern is created or if the existing one is replaced.

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 sentences, no fluff, but the parenthetical could be integrated. However, conciseness sacrifices necessary detail, making it less helpful.

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 two parameters, no output schema, and the need to describe cloning behavior, the description is incomplete. It does not explain what the result is, error conditions, or how the name parameter interacts with existing patterns.

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?

With schema description coverage at 0%, the description must explain parameters. It does not clarify what 'index' refers to (pattern index?) or the role of 'new_name' (optional? behavior when empty?). This leaves the agent guessing.

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 clearly states the action ('clone a pattern') and the scope ('copy all notes & channel grid bits'). The verb 'clone' is specific and distinct from sibling tools like pattern_create or pattern_delete.

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?

No guidance on when to use this tool versus alternatives (e.g., pattern_create, pattern_duplicate). It does not specify prerequisites or contexts where cloning is appropriate.

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