suno_list_personas

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

No annotations are provided, so the description carries full behavioral disclosure. It states the operation is a list (read-only) and describes the return value structure. For a simple list tool, this is sufficient, though no response format is given despite 'Has output schema' being true.

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?

The description is efficiently structured with a main statement, bullet-point use cases, and a return summary. Every sentence adds distinct value without redundancy, achieving high information density.

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 low complexity and the existence of an output schema (not detailed in description), the description adequately covers purpose, usage, and return type. It could mention pagination behavior or potential empty results, but overall 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%, so baseline is 3. The description does not add additional semantic meaning beyond repeating defaults already present in the schema. No edge cases or parameter interactions are discussed.

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 starts with a clear verb phrase 'List all saved artist personas' and specifies the scope 'for a user'. It distinguishes from sibling tools like suno_create_persona and suno_delete_persona by referencing the source tools and listing identification.

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?

Explicitly lists three use cases with 'Use this when:' bullet points, covering when to see personas, find a persona ID, or manage vocal styles. It does not state when not to use or name alternatives, but the guidance is clear for a listing operation.

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