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

Annotations already declare a read-only, non-destructive, open-world read. The description adds real value beyond that: the counts reflect the Insights page at call time (a freshness caveat), the top-tracks ordering (highest plays first), and an auth requirement (Cotlet API key with access to this app). That auth and freshness context is exactly the sort of extra behavioral detail that elevates it above the annotation baseline.

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 core facts are front-loaded, but the description repeats itself: 'for your profile or one track' and 'for the period you set' each appear twice across the first two sentences, and the metrics list is restated. It is not bloated, but it could be tightened without losing meaning.

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 output schema, the description carries the burden of describing returns, and it does: metrics list, top-tracks ordering, profile-vs-track scope, and the auth requirement. It is close to complete for a read-only insights call, missing only any pagination/limit behavior for top tracks.

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 to/from/track_id are already documented with defaults. The description reinforces the period and track-scoping semantics but adds no syntax, format, or default detail beyond the schema, so the baseline 3 is appropriate.

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?

It names a specific verb and resource with the concrete metrics returned (plays, likes, comments, reposts, downloads) and the two scopes (whole profile or one track). It does not, however, distinguish itself from the very similar sibling soundcloud_get_audience, leaving scope overlap ambiguous.

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?

It implicitly signals usage by saying the result is scoped to 'your profile or one track' via the from/to period, and that it is 'available to every account'. But there is no explicit when-to-use vs when-not, and no mention of how it differs from soundcloud_get_audience or soundcloud_get_track.

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