flat_edit_musicxml

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

With no annotations, the description carries the burden and does it reasonably: it declares this is a mutation that persists a new revision, and discloses the key transactional rule that a count mismatch aborts the write with nothing saved. It still omits permission requirements, whether the input is validated as well-formed MusicXML, and what happens to the previous revision.

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 core semantics are front-loaded and the edits shape follows immediately; almost every line earns its place. The example list of targets is brief and useful rather than padding, though the block could be tightened slightly.

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?

No output schema and no annotations, so the description should be self-sufficient; it covers the edit mechanics and atomic failure but leaves the purpose of the required description field, the dry_run preview behavior, and the response shape unexplained. Given four parameters and a mutation, that is a noticeable gap.

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 coverage is 0%, so the description must compensate, and it does well for the hardest parameter by spelling out the edits object shape (find/replace/count) and the exact-match semantics of count including its default. However, three required/optional parameters — score_id, description, and dry_run — receive no explanation at all, leaving half the contract undocumented.

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?

States a specific verb and resource: exact text substitution in the MusicXML, plus the side effect of writing a new revision. The use-case list (título, letra, dinâmicas, andamento) makes the scope concrete. It doesn't explicitly contrast with sibling flat_replace_measures or flat_update_metadata, which would be needed for a 5.

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?

Gives clear conditions for use through the example targets (title, lyrics, dynamics, tempo) and signals this is for surgical text substitutions. It does not state when to prefer the structural alternative (flat_replace_measures) or when this tool is invalid, so there are no explicit exclusions or named alternatives.

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