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

Annotations already declare readOnlyHint and openWorldHint, so the description adds real value beyond them: result ordering ('newest first'), pagination mechanics, and a credit cost ('Costs 1 credit'). This is meaningful operational context an agent needs before calling. It does not explain whether all uploads are covered (e.g. private/reposts) or the page size behavior.

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?

Three tight sentences, front-loaded with the resource definition before the pagination tip and cost. 'Artist tracks' is slightly redundant with the title but is immediately expanded. No filler.

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?

Covers ordering, pagination, and cost, which are the key call-time facts for a list tool. With no output schema, the description could say more about what each returned item contains and what limit controls, leaving gaps for a 4-parameter tool.

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 coverage is 50%: handle and cursor are documented in the schema, and the description reinforces cursor usage. However, limit (default 50) and cache_max_age are undocumented in both schema and description, so the description doesn't fully compensate for the coverage gap. Baseline 3 fits.

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 resource and scope: 'An artist's public uploads, newest first.' An agent can distinguish this from soundcloud_artist (profile) and soundcloud_track (single track) by the plural uploads framing. It stops short of naming those siblings explicitly, but the verb+resource is 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?

Provides pagination guidance ('Pass the cursor from the previous response to page') but gives no explicit when-to-use versus soundcloud_track or soundcloud_artist, and no preconditions. Usage is implied by the resource description rather than stated as guidance.

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