soundcloud_list_my_tracks

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

No annotations are provided, so the description must disclose behavioral traits. However, it fails to mention that this is a safe read operation, authentication needs, rate limits, or pagination behavior. Score 2 indicates insufficient transparency.

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 sentence, which is concise but lacks necessary detail. It could be expanded without becoming verbose. Score 3 indicates reasonable conciseness but not optimal.

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 one parameter and an output schema, the description is minimally adequate. However, it omits any mention of filtering, ordering, or pagination behavior. Score 3 reflects basic completeness with gaps.

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 description contains zero parameter information (schema coverage 0%). The schema itself documents the 'limit' parameter, but the description adds no value beyond the schema. Score 1 reflects the lack of parameter semantics.

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 clearly states the action (list) and resource (tracks) with scope (uploaded to your account), distinguishing it from siblings like soundcloud_get_track (single) and soundcloud_upload_track (upload).

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 explicitly state when to use this tool versus alternatives. While it implies use for listing own tracks, no guidance is given for not using it (e.g., for public tracks). Score 3 reflects implied usage without explicit context.

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