Add or remove entities in a MusicBrainz collection

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

Discloses authentication needs (OAuth with collection scope), dry-run behavior without confirm, and that no network call is made until confirmed. Aligns with annotations (readOnlyHint=false, idempotentHint=true). Does not mention rate limits or error responses, but overall adequate.

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?

Concise, well-structured: front-loaded with purpose, followed by prerequisites and key behavior details. Every sentence is informative with no redundancy.

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 no output schema, the description covers the dry-run preview and the need for confirm, but does not specify what the output looks like after mutation (e.g., success confirmation). Still sufficiently complete for a straightforward mutation tool with annotations providing idempotency and non-read-only hints.

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 coverage is 100%, so the description adds value by explaining how to obtain the collection MBID and the function of confirm. The entity type and action enums are clear from the schema, but the description provides practical usage context.

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 specific verbs 'Add or remove' and explicitly states it modifies MusicBrainz collections. It lists all entity types and is clearly distinct from sibling tools like search, lookup, or browse.

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?

The description explains the prerequisite OAuth scope, how to get the collection MBID, and the dry-run mechanism with confirm. It implicitly distinguishes from siblings by its unique mutative purpose, but could explicitly state when not to use it.

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