SunoMCP

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

No annotations provided, so description carries full burden. It mentions 'Converts' and 'visualizations' and notes the return includes 'Task ID', implying async behavior. However, it fails to explain the async workflow (that suno_get_task must be called to retrieve the final MP4) 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?

Well-structured with front-loaded purpose, followed by mechanism, use cases, and return value. Slight redundancy between 'Useful for sharing on social media' and the bullet points, but overall efficient with no fluff.

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 single-parameter conversion tool with existing output schema, the description is complete. It appropriately mentions the Task ID return value (hinting at async nature) without needing to fully document the output 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?

Schema coverage is 100% (audio_id fully documented in schema). The description text does not mention the parameter explicitly, but with complete schema coverage, no additional compensation is required. Baseline score applies.

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-resource pair ('Get an MP4 video version of a generated song') and distinguishes clearly from sibling tools like suno_get_wav or suno_get_midi by emphasizing 'video' and 'visualizations'. The scope is precisely defined.

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:' bullets covering video creation, social sharing, and visual representation scenarios. However, it lacks explicit exclusions or comparisons to alternatives (e.g., when to prefer get_wav over get_mp4 for audio-only needs).

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