Get playlist tracks (paginated)

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds pagination context and playlist-length guidance, but it does not explain page size, how to retrieve subsequent pages, or the shape of a page response.

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 two short sentences with no wasted words. The core purpose is front-loaded, and the alternative-routing note is placed immediately after.

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?

For a paginated tool with no output schema, the description is adequate but incomplete: it says tracks are listed page by page but never explains how pagination works, what a page contains, or how to use soundcloud_next_page. The parameter documentation and annotations cover most invocation needs, but return/pagination behavior is left for the agent to discover.

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 description itself adds no parameter-level meaning beyond the schema. Schema coverage is 67% because secret_token has no description, and the tool description does not compensate for that gap or clarify access/playlist semantics further.

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 verb and resource ('List the tracks of a playlist') and explicitly frames the pagination behavior. It also distinguishes itself from soundcloud_get_playlist by saying to prefer this tool for long playlists, so an agent can tell it apart from its sibling.

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 gives a concrete routing rule: prefer this over soundcloud_get_playlist for long playlists. This names the alternative and the condition that selects the tool, leaving little to inference.

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