Play Music Score

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

Annotations already declare readOnlyHint=true, and the description adds useful behavior beyond that: the seeded default demo (Beethoven excerpt), the requirement of abc_notation + notes[] for real OMR output, and the UI's bbox synchronization with playable score. This is richer than the baseline, though it doesn't cover all potential side effects or auth requirements (which are likely none here).

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?

Three sentences, each carrying distinct value: purpose, use case/details, and default/recipe. Information is front-loaded and every sentence earns its place; it is appropriate for a tool with 10 parameters.

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?

Despite no output schema, the description fully covers invocation context: the tool's purpose, when to use it, what to pass for real OMR, and the default demo behavior. The UI synchronization detail adds completeness for a rendering/playback tool, making it sufficient for an agent to invoke correctly.

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 100%, so baseline is 3, but the description adds value by specifying the parameter combination needed for real OMR ('abc_notation plus notes[]') and the default behavior when no input is provided. This goes beyond the field-level descriptions in the 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 clearly states the tool's function with a specific verb and resource: 'Render and play a PDF music-score extraction from semantic note events with normalized page bboxes.' It distinguishes this from sibling PDF viewing and UI tools by focusing on music-score playback and accessibility.

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 description gives an explicit use case: 'Use this when demonstrating non-text PDF accessibility.' It also provides a concrete recipe for real OMR output ('pass abc_notation plus notes[]'). However, it does not mention when not to use it or name alternative sibling tools, so it lacks full exclusions.

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