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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context — credit cost, that repeated requests may repurchase data, and that the response includes pagination info — but this conflicts with itself: 'at least 10 Nexscope credits' versus '1 credit per request'. The inconsistent pricing undermines the main value it contributes.

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 text is bloated and repetitious: after the clear opening sentences, it repeats the same purpose sentence almost verbatim ('SoundCloud Artist Tracks API View Pricing Gets tracks/songs for a SoundCloud artist by handle or URL') and restates pricing twice, apparently pasted from a marketing page. The useful content is front-loaded, but roughly half the text does not earn its place.

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 three-parameter read-only lookup with no output schema, the description covers the essentials: input modes, what is returned (profile, tracks, pagination), and cost behavior including repeat-request repurchasing. Only the contradictory credit figures and the absence of any note on page size keep it from being fully complete.

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 all three parameters (url, handle, cursor) are already documented in the schema, including the url-vs-handle alternative and how to get a cursor. The description only restates 'by handle or URL' and adds no format examples or constraints beyond the schema, which is the expected baseline.

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 uses a specific verb and resource: 'Fetches tracks/songs for a SoundCloud artist by handle or URL', and it also states the return payload (artist profile, track list, pagination info). It does not explicitly distinguish itself from the sibling social_soundcloud_artist (profile) or social_soundcloud_track (single track), but the resource scope is clear enough to separate them.

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 implies usage by saying results are looked up 'by handle or URL', but it gives no explicit when-to-use, when-not-to-use, or which sibling to pick when the caller only wants the artist profile versus the full track list. That routing decision is left to the caller's inference from the tool name.

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