transpose

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('transpose') but doesn't describe what gets transposed (e.g., current pattern, loaded data), whether it's destructive or read-only, or any side effects like rate limits or permissions. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero waste. It front-loads the core action ('Transpose notes') and specifies the mechanism ('by semitones') directly. Every word earns its place, making it easy for an agent to parse quickly.

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 complexity (a mutation operation with no annotations or output schema), the description is incomplete. It lacks details on what 'notes' refers to, the context of operation (e.g., modifies current pattern), and behavioral traits like safety or response format. This is inadequate for a tool that likely alters musical data, leaving the agent with insufficient guidance.

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 input schema has 100% description coverage, with one parameter 'semitones' fully documented. The description adds no additional parameter semantics beyond implying that semitones are used for transposition, which is already clear from the schema. This meets the baseline score of 3 for high schema coverage without extra value from the description.

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 'Transpose notes by semitones' clearly states the action (transpose) and target (notes) with a specific mechanism (by semitones). It distinguishes from siblings like 'apply_scale' or 'generate_scale' by focusing on pitch shifting rather than scale application or generation. However, it doesn't specify what 'notes' refers to (e.g., musical notes in a pattern or sequence), leaving some ambiguity compared to more specific sibling tools.

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. It doesn't mention prerequisites (e.g., needing notes to transpose), exclusions (e.g., not for tempo changes), or direct alternatives among siblings like 'apply_scale' for key-based adjustments. The agent must infer usage from the tool name and context alone.

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