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

Annotations already establish that this is a safe read-only operation, so the description is not required to carry the safety burden. It adds useful behavioral detail beyond annotations by describing the unfiltered overview contents and how filtered calls produce note rows and mark IDs, though it does not cover error behavior or permission requirements.

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 description is only a few sentences, front-loads the core purpose, and then uses compact parentheticals to explain conditional output. Every sentence contributes useful information with no filler.

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 carries the burden of explaining return content, and it does so for both unfiltered and filtered modes. It is mostly complete for a read tool, though minor details such as error cases or exact response framing are left implicit.

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 high at 89%, so parameter documentation is largely handled by the input schema. The description adds conceptual meaning around filters and note_columns, but it does not supplement the individual parameter semantics enough to exceed the baseline for a well-described schema.

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 starts with a specific verb and resource ('Read a saved score') and clearly explains the two operating modes: unfiltered overview versus filtered note/mark listing. It does not explicitly differentiate itself from nearby siblings such as list_scores, open_score, or read_notation_view, so it falls short of 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?

It explains what happens with no filters versus filters, which gives implied usage guidance for choosing between an overview and a scoped note listing. However, it never names alternatives or states when another sibling tool would be more appropriate, leaving the agent to infer routing.

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