Artist

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

Adds context annotations do not carry: it warns about paid API credit consumption, states the confirm=true gate, and preempts the surprising readOnlyHint=false by clarifying that the read-like POST does not publish to social platforms. It does not matter that annotations mark it non-read-only; the description explains the nuance rather than contradicting it.

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?

Front-loads the primary action and scope in the first sentence, then appends cost and no-publish caveats. Efficient overall, though the trailing 'etc' and multi-clause final sentence are slightly loose.

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 4-parameter read tool with full schema coverage, it covers purpose, identification inputs, credit cost, and the confirm gate, and hints at the returned fields (id, name, followers). With no output schema, a fuller description of the return shape would help, but nothing essential for a correct call is missing.

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 url, handle, account and confirm are already documented in the schema. The description merely restates the handle-or-URL choice and the confirm requirement without adding format or syntax detail, so the baseline of 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?

States a specific verb (fetches) and resource (detailed information about a SoundCloud artist) plus the two ways to identify it (handle or URL). It implicitly distinguishes itself from soundcloud_artist_tracks and soundcloud_track by promising artist metadata rather than tracks, but never explicitly names or differentiates from those siblings.

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 a usage prerequisite (requires confirm=true for the credit-consuming call), which is real when-to-use guidance. However, it names no alternatives and gives no conditions selecting this tool over soundcloud_artist_tracks, soundcloud_track, or a generic search, so the routing guidance is only implied.

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