append_live_measures

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic mutation—appending empty measures—without mentioning side effects, connection requirements, or failure modes. It is not misleading, but it is sparse for a score-mutating operation.

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 three short lines with the core action front-loaded and the parameter documentation in a minimal Args block. There is no filler or redundant 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?

For a simple one-parameter append tool with an output schema present, the description is essentially complete: the agent knows the action, the target, and the parameter meaning. It omits explicit prerequisites like being connected to a score app, but the 'live score' wording and sibling context partially cover that.

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 schema only provides an integer named 'Count' with a default of 1, while the description adds the meaningful semantic 'How many measures to append' and restates the default. This fully compensates for the 0% schema description coverage, though it does not add constraints such as a minimum positive value.

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 uses a specific verb ('Append'), a precise object ('empty measures'), and a target ('the end of the live score'). This makes the operation unmistakable and clearly distinct from sibling tools like add_live_note or set_live_barline.

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 intended use is implied by the operation itself, but the description does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites such as being connected to a score app. It gives no exclusion or when-not-to-use guidance.

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