SunoMCP

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

With no annotations provided, the description carries the full burden. It discloses the async nature via 'Returns: Task ID' and callback_url parameter context, explains the consistency guarantee mechanism, and clarifies the two-step workflow. Minor gap: doesn't explicitly state this creates new resources or mention polling patterns if callback omitted.

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?

Efficiently structured with purpose first, value proposition second, bulleted use cases, prerequisite instruction, and return value. Every sentence serves selection or invocation logic; no redundant text despite multiple paragraphs.

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?

For a workflow-dependent tool with 5 parameters, the description adequately covers the persona prerequisite, cross-tool dependencies, return values (Task ID), and specific use cases. With output schema available, the brief return description is sufficient.

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%, establishing baseline 3. The description adds crucial semantic context by specifying that persona_id must be obtained from 'suno_create_persona' tool, linking parameters across the tool workflow. It also clarifies that the prompt describes the music while the persona defines the voice application.

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 ('Generate') + resource ('music') + mechanism ('saved artist persona'), clearly distinguishing this from generic generation tools like 'suno_generate_music' by emphasizing 'consistent vocal style' and persona reuse.

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:' criteria with three concrete scenarios (multiple songs with same style, album creation, voice reuse). Also names the prerequisite tool ('suno_create_persona') and workflow sequence, effectively defining when-not-to-use (before creating a persona).

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