flat_upload_revision

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

With no annotations, the description carries the full burden. It does disclose two important traits: the operation destroys and overwrites the entire score, and the result is persisted as a new revision (so prior content remains recoverable). It says nothing about permissions, precedence between the two input modes, or failure behavior for an invalid score_id.

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 compact sentence (plus line break) that front-loads the action and its effect. No filler; the only loss is that brevity comes at the cost of the missing parameter and alternative guidance.

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?

There is no output schema and no annotations, and 4 parameters sit at 0% schema coverage. The description covers the core content input and the revision semantics, but the required description parameter, score_id, mutual exclusivity of musicxml vs file_path, and guarantees about the previous revision are all unaddressed.

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 clarifies the accepted formats and sources for musicxml/file_path (.musicxml/.xml/.mxl/.mid, local path or inline text), but leaves score_id and the required description parameter entirely undefined, and never says which of the two content inputs takes precedence.

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: replaces the entire score ('Substitui a partitura inteira') with a full MusicXML document and records it as a new revision. The word 'inteira' implicitly separates it from flat_replace_measures and flat_edit_musicxml, though no sibling is named.

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?

Usage is implied rather than stated: full-score substitution versus the partial-edit siblings is inferable from 'inteira', but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must reason about scope to pick this over flat_replace_measures or flat_edit_musicxml.

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