Get users who liked / reposted a track

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'List' phrasing adds no new safety behavior. The description provides no additional behavioral context such as pagination behavior, authentication requirements, or whether both kinds can be requested together.

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 a single, front-loaded sentence with no filler. It communicates the core purpose efficiently and every word contributes 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?

Given the low parameter complexity, rich schema descriptions, and strong safety annotations, the description is largely sufficient for an agent to select and invoke the tool. The lack of an output schema is partly mitigated by the clear 'List the users' phrasing, though pagination behavior is not explicitly covered.

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 has 100% coverage with meaningful descriptions for all parameters, including the kind enum. The description itself adds no parameter semantics beyond what the schema already provides, so the baseline score of 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?

The description states a specific action ('List') and a specific resource ('users who liked or reposted a track'). It clearly differentiates this tool from sibling tools like soundcloud_get_track_comments or soundcloud_get_track by focusing on engagement users rather than track metadata or comments.

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 does not state when to use this tool versus alternatives, nor does it provide exclusions or conditions. The only usage signal is implicit in the verb 'List' and the tool name, which is not enough to guide an agent through sibling tools like soundcloud_set_like or soundcloud_get_track_comments.

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