SunoMCP

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

With no annotations, the description carries full burden. It discloses the async pattern by noting the return includes a 'Task ID', hinting at polling requirements. However, it lacks details on processing time, error conditions, whether source tracks are consumed/destroyed, or rate limits.

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?

Well-structured with clear sections: purpose statement, sibling differentiation, usage conditions, and return value. No redundant words; every sentence earns its place by adding distinct context not present in the schema.

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?

Appropriate for a 3-parameter tool with output schema. Mentions the Task ID return value indicating async behavior, though it could explicitly state that users must poll suno_get_task for completion given the sibling tools available.

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%, documenting all three parameters (mashup_audio_ids, model, callback_url) including the constraint for '2 or more song IDs'. The description reinforces the 'two or more songs' requirement but doesn't add semantic meaning beyond the schema's clear documentation.

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 opens with a specific verb ('Create') and resource ('musical mashup'), and explicitly distinguishes from sibling tool suno_mashup_lyrics by clarifying 'this blends the actual audio' versus lyrics.

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?

Provides explicit 'Use this when:' bullet points covering DJ-style mashups and combining melodies. Distinguishes from the lyrics mashup sibling, though it could clarify when to use this versus suno_concat_music or suno_cover_music.

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