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

Annotations already establish read-only and non-destructive behavior, and the description adds that no user account is needed and specifies exact output formatting via list_label. It does not mention pagination or data freshness, but for a read-only list this is reasonable; no contradiction with annotations.

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 front-loaded with the core purpose and then gives precise output formatting rules and examples. It is a bit longer than strictly necessary, but each sentence contributes operational guidance, so it earns its place.

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?

With no parameters and no output schema, the description still tells the agent exactly what to print (list_label) and shows concrete examples. For a simple read-only list tool, this is complete enough to call and render correctly.

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 tool has zero parameters and the input schema is empty, so there is nothing for the description to add beyond the schema. Baseline of 4 is appropriate for a no-parameter tool; no param documentation burden.

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?

States the exact operation (list) and resource (active SoundBreak AI artists/cowriters) and clarifies they are for co-writing. This distinguishes it from siblings like get_artist_details and list_my_songs without needing to inspect schemas.

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 'No user account required' note gives useful access context, and 'available for co-writing' implies when to call it, but the description never explicitly routes to alternatives such as get_artist_details for individual artist info or create_song_generation. There are no when-not-to-use or alternative conditions.

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