set_time_signature

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool. It implies a persistent change from the given bar onward and hints at a read-back/verification behavior for simple n/d values, but it is silent on permissions, reversibility, and what happens to existing signatures after that bar.

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?

It is short and mostly front-loaded, but the opening is a verbless fragment and the closing sentence ("Single n/d values are read back to confirm") is telegraphic enough that its meaning is unclear. Little is wasted, but clarity suffers from the terseness.

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 mutation tool with no annotations, no output schema, and 0% schema description coverage across three parameters, the description does not supply enough: `flow` is undocumented and the behavioral/verification sentence is ambiguous. An agent could invoke it but might mis-scope the change.

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?

Schema description coverage is 0%, so the description must compensate. It usefully documents the accepted value syntax (n/d, compound 2+3/8, and the c/cut symbols) and implicitly ties the change to the `bar` parameter, but the `flow` parameter is entirely unaddressed in both schema and 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 names the resource (time signature) and its scope ("from a bar on"), and gives concrete value examples like 3/4, 6/8 and 2+3/8. However, it never states the action as a verb — the reader must infer "set" from the tool name — and the second sentence about read-back is opaque rather than clarifying.

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?

There is no guidance on when to use this versus alternatives such as set_key_signature or add_barline, no prerequisites, and no note on whether the change is scoped to a single flow. The "from a bar on" phrase hints at scope but is not usage guidance.

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