motif_develop

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

The description focuses on the mathematical transformations but does not disclose any behavioral traits such as whether the input notes are mutated in place, whether a new object is returned, what side effects occur (if any), or if the tool has any restrictions (e.g., destructive actions). With no annotations provided, this gap is significant.

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 compact and well-structured. It opens with the primary purpose, then enumerates the transformation types with concise clarifications. No redundant sentences or fluff; every sentence contributes useful information.

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 adequately explains the transformation logic, but it omits critical context such as the expected input format for 'notes', the return value (especially since no output schema is provided), and the behavior of 'offset_beats'. These omissions could leave an agent uncertain about how to invoke the tool correctly and what to do with the result.

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?

The description adds meaning to some parameters (e.g., semitones, axis_pitch, factor, and the sequence_up/down behavior) that are not fully explained in the schema. However, it does not clarify the 'notes' format or the purpose of 'offset_beats', leaving those parameters under-specified. It improves coverage but is not complete.

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 tool's purpose: 'Transform a motif (set of notes) into a variation.' It specifies the exact resource (motif/notes) and action (transform), and lists all supported transformations, making the tool's function 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?

No guidance is given on when to use this tool versus alternatives (e.g., compose_variations or other composition tools). The description explains how each transformation works but never addresses the context or selection criteria, leaving the agent without direction on when this tool is the appropriate choice.

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