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

Annotations already establish this is a safe read (readOnlyHint=true, destructiveHint=false), and the description adds meaningful data semantics beyond that: results are capped at top 50, sorted highest first, top_listeners counts only signed-in listeners, and plays from the user's own account are excluded. The Artist Pro/permission/API-key constraints add real behavioral context. It doesn't cover pagination or output shape, keeping it at 4.

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?

Front-loaded with the core purpose, which is good, but 'Needs Artist Pro' is repeated twice within a short span and the sentences are somewhat list-like. The repetition wastes space without adding information.

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?

No output schema exists, so the description carries the burden of describing returns, and it does explain the top-50 cap, ordering, and what each breakdown represents. It is adequate for a read-only analytics call, though it could note whether smaller result sets are possible.

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 description coverage is 100%, so all four parameters (from, to, track_id, breakdown) are already documented in the schema. The description reinforces 'one breakdown and any period you set' but adds no format or syntax detail beyond the schema. Baseline 3 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?

States a specific verb (get/return) and resource (audience breakdown) and enumerates the four breakdown types. It clearly says it returns the top 50 for one breakdown. It does not differentiate itself from the sibling soundcloud_get_insights, so it stops short of a 5.

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 prerequisites (Artist Pro required, permission error otherwise, valid Cotlet API key) and the period scope, which helps decide whether the call can succeed. However it never says when to prefer this over soundcloud_get_insights or other insight tools, so selection guidance is only implied.

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