set_pattern

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

With no annotations at all, the description carries the full behavioral burden for a mutation tool. It never states whether omitted/optional params are left unchanged (critical here since name, color, and length all default to null), what happens with an invalid pattern id, or whether changes are undoable. The 'length 0 = automatic' note is genuinely useful behavior, but it is the only one.

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?

One short, front-loaded sentence with no filler; the actionable clarification is appended where it is needed. It is terse but not padded — the brevity is a virtue here, though it edges into under-specification.

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?

A 5-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage needs considerably more: partial-update semantics, the unit parameter's effect, and what the call returns. The description covers four of five params only loosely and omits `unit` entirely.

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 0% across 5 parameters, so the description must compensate and largely does not. It explains pattern as an id and gives the length=0 sentinel, but the enum parameter `unit` (beats/ticks) is never mentioned, and the null-default semantics of name/color/length are left implicit.

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 states a specific verb set (rename, recolor, set length) against a specific resource (pattern, identified by id), so the agent knows exactly what mutation occurs. It doesn't differentiate itself from siblings like set_channel or set_clip, but the action is unambiguous.

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?

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. The only guidance is the inline 'length 0 = automatic' rule, which is a parameter convention rather than usage context.

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