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

Annotations already declare readOnlyHint and destructiveHint, so the bar is lower. The description adds useful context beyond annotations: the tool only handles explicitly published resources and must not be used to infer rights or availability. This aligns with openWorldHint=false rather than contradicting it.

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 compact and front-loads the primary usage condition. The closing sentences about not inferring rights, ownership, licensing, and availability are somewhat redundant, but they do not add meaningful bloat.

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?

For a simple one-parameter read-only lookup with an output schema present, the description provides the key usage boundary and an important closed-world constraint. It could be improved by clarifying what an 'explicitly published sheet-music resource' is and by defining the id parameter, but overall it is sufficient for a low-complexity tool.

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?

The schema has 0% description coverage for the single required 'id' parameter, and the description does not explain what kind of identifier it is, where it comes from, or how it maps to a sheet-music resource. The only implicit hint is that 'id' identifies the sheet-music resource mentioned in the description, which is minimal compensation for the complete lack of schema documentation.

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 specific action ('check for') and a specific resource ('explicitly published sheet-music resource'), which distinguishes it from siblings like get_track or search_music. However, the verb 'check for' is slightly less precise than the title's 'Get', leaving some ambiguity about whether it retrieves the resource or verifies its existence.

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 opens with an explicit 'Use this when...' condition targeting explicitly published sheet-music resources. It also gives clear negative guidance about not inferring ownership, licensing, or unpublished availability, but it does not name alternative sibling tools or state when not to use this tool beyond those constraints.

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