SunoMCP

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

With no annotations provided, the description carries the full disclosure burden. It adequately previews the return value ('Complete guide with section markers, examples, and tips'), but omits other behavioral traits like whether the guide is static/cached, idempotent, or if there are rate limits for retrieving documentation.

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?

Four sentences efficiently cover purpose, mechanism, value proposition, and return value. Every sentence earns its place without redundant filler. The 'Returns:' section is appropriately brief given the existence of an output 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?

Given the tool's simplicity (no parameters, read-only guide retrieval) and presence of an output schema, the description provides sufficient context for invocation. It could marginally improve by explicitly stating this is a zero-configuration reference call.

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?

The input schema contains zero parameters, which per the rubric establishes a baseline score of 4. The description correctly does not invent parameters, though it could explicitly note that no configuration is required to retrieve the guide.

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?

Description opens with a specific verb-resource pair ('Get guidance on formatting lyrics') and clearly scopes it to 'Suno music generation.' It effectively distinguishes from siblings like suno_generate_lyrics (which creates lyrics) by emphasizing this provides 'guidance' and 'format' structure rather than generating content.

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 benefit of using the tool ('helps Suno understand the song structure and generate appropriate melodies'), implying it should be consulted before submitting lyrics to generation tools. However, it lacks explicit guidance on when to use this versus suno_generate_lyrics or whether users need this when using the automatic lyric generator.

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