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. The description adds genuinely new context: the score owner, view, and revision are validated before rendering, and no musical edit occurs. It does not describe return shape or paging, but with annotations carrying the safety burden this is solid added value.

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 compact sentences with the core action front-loaded and the no-edit caveat second. No filler, though the second sentence spends its space on validation rather than the more useful view/revision semantics.

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 exists, and the description only loosely characterizes the return as 'rendered numbered-notation pages' without format, page size, or paging behavior. Combined with an undescribed required 'view' string, the definition leaves real gaps an agent would hit on first invocation.

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 and largely does not. It gestures at 'view' and 'revision' but never explains what a view is, what values 'view' accepts (0 enums, required string), or what form 'score_id' takes. An agent still cannot fill the required 'view' parameter confidently.

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: 'Return rendered numbered-notation pages' for the current or a specified saved revision. That is clearly distinct from mutating siblings like edit_score or set_notation_view. It stops short of naming which sibling to use for related reads (get_score, read_score_panel).

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 phrase 'current or specified saved revision' implies when the revision parameter matters, and 'no musical edit is performed' clarifies the read-only intent against edit siblings. There is no explicit guidance on when to prefer this over read_score_panel or get_score, so usage must be inferred.

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