Browse MusicBrainz entities linked to another

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. The description adds value by explaining it returns a complete paged set (not fuzzy), and mentions the data source (MusicBrainz) and pagination constraints. No contradictions.

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 efficient sentences: one long sentence with purpose and examples, then two short sentences contrasting with search and providing pagination guidance. Every sentence is necessary and well-placed.

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?

No output schema, but the description covers purpose, parameter usage, pagination, and read-only nature. It does not describe the return format (e.g., list of entities with IDs/names), which is a minor gap given the tool's simplicity and high schema coverage.

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%. The description adds meaning beyond the schema by providing usage examples linking entity and linkedBy parameters (artist→release, release→recording, etc.) and explaining 'inc' for extra detail.

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 uses a specific verb+resource ('List all entities of one type directly linked to a given entity') with concrete examples (e.g., 'every release by an artist'). It clearly distinguishes from the sibling tool 'musicbrainz_search' by contrasting fuzzy matching vs. complete paged sets.

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?

Explicitly states when to use (to get the complete paged set of linked entities) and when to use an alternative ('unlike search, which ranks fuzzy matches'). Provides pagination details ('limit/offset to page, max 100/page') and hints about 'inc' for extra detail.

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