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

No annotations exist, so the description carries the burden, and it does disclose useful behavior: the 2-credit cost, free on empty results/failures, cache behavior with cache=true, and the opaque-cursor/native-window pagination note. It does not cover output shape or error details, but for a read/list tool this is a solid level of disclosure.

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 short and front-loaded, but it is somewhat cryptic and redundant. Phrases like 'native-window when the api-v2 page ends' are unexplained jargon, and 'Costs 2 credits' repeats the earlier credit information without adding much value.

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 list tool with well-documented parameters and no output schema, the description covers the essential operational concerns: cost, caching, pagination, and failure charging. It lacks a plain statement of what fields the returned tracks will contain, but the tool name and 'track list' phrase make the primary purpose unambiguous.

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 all four parameters (url, cache, limit, cursor). The description adds a bit of context around caching and cursor opacity, but it largely repeats or restates what the parameter descriptions already provide.

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 identifies the resource ('artist track list') and the action (retrieve/list), and the name 'soundcloud_artist_tracks' reinforces this. It does not explicitly differentiate from siblings like soundcloud_artist or soundcloud_track, but the phrase makes the tool's scope reasonably clear.

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?

Usage context is implied rather than explicit: the name and 'Artist track list' suggest this is for getting a SoundCloud artist's tracks, as opposed to artist profile details or a single track. There is no explicit when-to-use guidance or mention of alternatives such as soundcloud_artist or soundcloud_track.

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