APIbase

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing this as a safe lookup operation. The description adds valuable context about the specific fields returned (artist credits, labels, media formats), compensating partially for the lack of an output schema, but does not address rate limits, caching, or error conditions.

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 a single, efficient sentence that is front-loaded with the action verb. Every element serves a purpose: the action, the key identifier, the specific return data types, and the data source. No extraneous words or redundant phrases.

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?

Given this is a simple single-parameter lookup tool with strong annotations, the description is appropriately complete. It effectively compensates for the missing output schema by enumerating the specific data fields returned (artist credits, labels, media formats), allowing the agent to understand the tool's value proposition without seeing the response structure.

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?

With 100% schema description coverage, the baseline is appropriately met. The description reinforces the mbid parameter by mentioning 'MusicBrainz ID' but does not add significant semantic meaning beyond what the schema already provides (UUID format, return info).

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 specific action (Get full release details), the required identifier (MusicBrainz ID), and the specific data returned (artist credits, labels, media formats). It implicitly distinguishes from music.releases.search by requiring an ID versus query terms.

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?

While the description implies you need a MusicBrainz ID (mbid) to use this tool, it lacks explicit guidance on when to use this versus music.releases.search or music.recordings.search. The prerequisite of having an MBID is clear from the parameter, but no explicit when/when-not rules are stated.

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