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

The description frames a pure retrieval ("Get the CUE SHEET", "Hand this over"), yet the annotations declare readOnlyHint=false and idempotentHint=false, i.e. a state-changing, non-repeatable operation. That directly contradicts the read-only nature the description asserts. The provenance sentence ("AINSOF controls master and publishing, so these are stated facts, not estimates") is genuinely useful context, but the annotation mismatch is a hard rule violation.

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, front-loaded with the payload contents, then the usage trigger, then the provenance caveat. Every sentence earns its place and nothing is repeated from the schema 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 usefully enumerates the returned fields and their authority, which is exactly what the agent needs to decide whether this tool answers the user's question. It omits failure behaviour (e.g. unknown track) and any note about the identifier form, keeping it just short of complete.

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 only one parameter and the schema describes it fully ("a track_id, or the track's title"), so the baseline is 3. The description adds nothing about the accepted identifier forms, so it neither compensates nor detracts.

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 gives a specific verb and resource ("Get the CUE SHEET for a track") and then enumerates exactly what the sheet contains — album, catalog number, ISRC, tempo, key, publisher, writers with IPI/society/share. That is far more specific than the neighbouring get_track/search_music, so an agent can distinguish it without opening any schema.

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?

"Hand this over when the user needs delivery paperwork, rights information, or asks who wrote it" is an explicit when-to-use trigger tied to user intent. It stops short of naming a when-not condition or an alternative sibling, so it is clear context rather than full routing guidance.

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