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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine context beyond that — that the state is app-only and exists to synchronize an existing panel — but says nothing about permissions, staleness, or whether the pending preview is server- or client-side.

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 sentences with no filler; the payload contents are front-loaded in the first sentence and the scoping note second. Nothing is repeated from the title or annotations.

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, the description does the right thing by naming the three pieces of state returned, which is what an agent needs to interpret the response. It falls short only on the meaning of score_id and on any indication of what happens if no existing panel state is found.

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?

There is one parameter with 0% schema description coverage, and the description never mentions score_id or what identifier form it expects. With coverage this low the description is expected to compensate for the schema, and it does not.

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?

"Read the saved score revision, pending preview and notation display preference" names a concrete verb and enumerates the exact state payload returned, which is more specific than a generic "get state." It does not differentiate itself from the very close sibling read_score_panel or from read_notation_view, so an agent still has to guess which of the trio supplies what.

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?

"This app-only state supports synchronization of an existing panel" implies the usage context (syncing an already-open panel) but never states when to prefer this over read_score_panel, get_score, or read_notation_view. No exclusions or prerequisites are given, so usage is only inferable.

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