SunoMCP

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

No annotations provided, so description carries full burden. Discloses return value structure ('Table of all models with their version, limits, and features') and enumerates specific model versions with capabilities, which is essential behavioral context for this domain.

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 usage context, detailed model comparison bullets, and return specification. Every element serves the agent's decision-making process; model specs are essential data despite length.

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 the complex model ecosystem (6+ versions), the detailed comparison table provides critical contextual completeness. Output schema exists but description appropriately summarizes it while adding rich domain-specific details (duration limits, quality tiers).

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?

Zero parameters present with empty input schema. Per guidelines, baseline score is 4 for zero-parameter tools. Description appropriately focuses on return value semantics rather than non-existent parameters.

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?

Explicitly states 'List all available Suno models and their capabilities' with specific verb and resource. Clearly distinguishes from action-oriented siblings (generate, extend, cover) by focusing on metadata/discovery rather than music manipulation.

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 clear when-to-use guidance: 'Use this to understand which model to choose for your music generation.' Implicitly contrasts with generation tools but lacks explicit 'when not to use' or direct references to sibling dependencies.

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