add_drum_pattern

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

The description explains pattern tiling over length and kit mapping, but lacks disclosure of whether notes overwrite existing content in the clip, what happens with invalid indexes, or error handling. No annotations exist to offset this lack.

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 concise and well-structured, with a clear opening statement and bulleted parameter list. It could be slightly more compact but is efficient for the information provided.

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?

The description covers pattern logic, parameter details, and default mappings. However, it omits prerequisites (e.g., clip must exist, track and clip indexes must be valid) and does not clarify if the clip should be empty. No output schema to supplement.

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 0% schema coverage, the description adds meaning for pattern (enumerates values), kit_map (structure and defaults), velocity (range), and length (tiling). However, it does not explain track_index or clip_index beyond listing them in 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?

The description clearly states 'Write a preset drum pattern into an existing clip' and enumerates specific preset patterns (four_on_floor, trap, etc.), making the tool's purpose unambiguous. It distinguishes from siblings like add_notes_to_clip and load_drum_kit.

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 implies usage for preset drum patterns via parameter values, but does not explicitly provide when-to-use or when-not-to-use guidance compared to alternatives like add_notes_to_clip. Usage context is only implied.

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