Insert Measure

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

No annotations are provided, so the description carries the full behavioral burden. It reveals only that this is a mutation, and says nothing about whether subsequent measures shift or renumber, whether an open score or cursor is required, or whether the change is undoable.

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?

A single short sentence, front-loaded with the verb and resource, with the positional qualifier immediately after. There is no filler and nothing is buried.

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?

For a zero-parameter tool with no output schema, the description covers what it does and where the measure lands. It is still silent on preconditions (open score or valid cursor) and on side effects such as renumbering or shifting existing measures, which matter for a mutation in a score-editing tool.

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 zero parameters the schema is trivially complete, giving a baseline of 4. The description usefully adds that placement is derived from the current cursor position rather than any argument, which is real information for a zero-param tool.

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?

"Insert a measure at the current position" gives a specific verb (insert) and resource (measure), and the phrase "at the current position" implicitly distinguishes it from append_measure, which would add at the end. It never names that sibling explicitly, so differentiation is inferred rather than stated.

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 phrase "at the current position" implies usage at the cursor location and hints at the contrast with a positional alternative, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer the routing decision from the position wording alone.

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