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

The readOnlyHint annotation already establishes this is a safe read, so the description only needs to add context. It does add useful content by naming what comes back (track metadata, provenance hash, EU AI Act compliance status, on-chain anchor info), but says nothing about error behavior when a credential_id does not exist or whether results are cached/live.

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 first sentence is front-loaded and states the purpose immediately, and the return-value list adds value. The trailing Args block duplicates the schema verbatim and is the one mildly wasteful element.

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 one required parameter, full schema coverage, an output schema, and a readOnlyHint, the definition covers what an agent needs to invoke it. The only real gap is sibling differentiation, which the description leaves out.

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 100% and the single parameter is documented as 'UUID of the music credential' in the schema. The description's Args block restates that identically without adding format constraints or fallback behavior, so the baseline 3 applies.

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 full provenance details for a music credential') and enumerates the returned content, so the purpose is unambiguous. However, it never distinguishes itself from close siblings such as mt_verify_music_credential or mt_issue_music_credential, which an agent must otherwise infer.

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?

There is no statement of when to use this tool versus mt_verify_music_credential or mt_get_badge, nor any prerequisites or exclusions. The retrieval intent is only implied by 'Get full provenance details'.

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