Get user / artist

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the 'public' qualifier, which suggests no special authentication is needed, but it does not discuss output shape, error behavior, or rate limits. There is no contradiction with the annotations.

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 a single front-loaded sentence. It leads with the action and resource, then provides a useful field list without unnecessary padding.

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 profile fetch with a fully documented schema and rich annotations, the description is nearly complete. It enumerates the returned profile fields, which is helpful since there is no output schema, though it does not specify error cases or exact response structure.

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?

Input schema coverage is 100%, so the schema already documents the user and raw parameters thoroughly. The description adds no parameter-specific semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 opens with the action 'Fetch' and clearly identifies the resource: a user's public profile. It enumerates the profile contents, which helps distinguish it from sibling tools like soundcloud_list_user_content, soundcloud_search_users, and soundcloud_me.

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 the tool is for retrieving a specific user's public profile, but it does not explicitly define when to use it versus alternatives. It does not mention when to prefer soundcloud_me, soundcloud_resolve, or soundcloud_list_user_content.

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