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

Annotations already establish readOnly/non-destructive/openWorld, so the bar is lower. The description earns credit by disclosing return content (privacy, release date, lifetime plays/likes/comments/reposts), pagination behavior (200 per page, cursor round-trip), and the API-key-with-app-access auth requirement.

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?

Dense and front-loaded, leading with what is returned. Minor redundancy: 'newest first' appears in both the opening phrase and the next sentence, which is wasted repetition in an otherwise tight definition.

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 explaining returned fields, and it does so comprehensively (privacy states, release timing, count types, page size, cursor handling, auth). Nothing needed to call it correctly is missing.

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 the schema already documents limit, cursor and the privacy enum, setting the baseline at 3. The description's 'pass next_cursor back as cursor' and 'pages hold up to 200' largely restate schema content rather than adding new 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?

States a specific verb and resource ('Lists the tracks on your profile, newest first') with clear scope. An agent can distinguish it from siblings like soundcloud_get_track (single track) and soundcloud_get_insights (period-based analytics) without opening any schema.

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?

Routes the agent to soundcloud_get_insights for period-based counts versus this tool's lifetime counts, and explains the privacy filter values including the scheduled case. It lacks explicit when-not-to-use framing, but the alternative for analytics is named clearly.

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