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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description does add cost behavior ('Repeated requests may purchase data again', credit consumption), which is genuinely useful context not in annotations. However, the pricing statements are self-contradictory ('at least 10 Nexscope credits' vs '1 credit per request'), which muddies rather than clarifies the cost model.

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?

After a strong one-sentence lead, the text degrades into duplicated pricing boilerplate ('SoundCloud Artist API View Pricing', 'Actual supplier units are reported per request', 'Examples are not guaranteed prices') that repeats the same idea three times and contradicts itself on cost. The purpose statement is front-loaded but roughly half the text is noise.

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 simple two-parameter lookup with no output schema, the description gives enough to call it: identifier forms accepted and a sketch of returned metadata. What's missing is any disambiguation from the soundcloud_track / artist_tracks siblings and a coherent cost statement, so it is adequate but not 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 coverage is 100% and both parameters are self-documenting, so the schema carries the semantics. The description's phrase 'by its handle or URL' adds only a hint that either identifier works, without stating that at least one of the two optional parameters must be supplied. Baseline 3 applies.

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 opening sentence names a specific verb and resource ('Fetches detailed information about a SoundCloud artist by its handle or URL') and even lists returned fields (id, name, followers), which cleanly separates it from social_soundcloud_track. It never explicitly distinguishes itself from the sibling social_soundcloud_artist_tracks, so it falls short of a 5.

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?

There is no when-to-use guidance beyond the implicit 'look up an artist.' Nothing tells the agent when to pick this over social_soundcloud_artist_tracks or social_soundcloud_track, and no prerequisites or exclusions are stated.

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