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

Annotations only say readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description goes beyond that by scoping the mutation to the view only ('without changing any note or the revision') and by disclosing a cross-surface side effect: workspace and embedded views share the choice, and a prepared panel plus its Download PDF follow it. That is exactly the kind of downstream-state context the annotations cannot carry.

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?

Two tight sentences, zero filler, with the core action front-loaded and the consequence of the setting appended. Nothing is repeated from the schema.

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?

With no output schema and only two parameters, the description covers what changes and what does not, which is the main risk. It is still silent on prerequisites (does a score need to be prepared or open first?) and on score_id semantics, so it is adequate but not complete.

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 50%: the view parameter is fully enumerated in the schema, and the description repeats the staff/jianpu distinction, so it adds little there. score_id has no description in either the schema or the description, leaving its semantics (saved score vs. prepared panel) 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?

The description states a concrete action and object: render the score as staff notation or jianpu. It is unambiguous about what the tool does, though it never names the closely related sibling read_notation_view, so the agent must infer the split between reading and setting the view.

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 clause 'without changing any note or the revision' implicitly tells the agent this is the right tool for a display-only change rather than edit_score or revise_score. However, no alternative is named and there is no statement of when not to use it, such as whether a prepared panel must exist first.

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