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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, open-world safety profile is covered. The description adds only that the profile is public and what fields it returns; it says nothing about auth needs, rate limits, or behavior on private/deleted accounts. Adequate but thin against the annotation baseline.

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?

Two sentences, front-loaded with the core action and then routing guidance. The field enumeration is somewhat redundant given an output schema exists, but it is brief and does not bloat the text.

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 single-parameter read tool with a full output schema and read-only annotations, the description is essentially complete: purpose, scope, and sibling routing are all present. Only marginal behavioral context (private accounts, error cases) is absent.

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% and the single url parameter is documented in-schema as a full soundcloud.com profile URL. The description implies the input targets a user/artist profile but adds no format or syntax detail beyond the schema, so the 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?

States a specific verb+resource (fetch a public SoundCloud user/artist profile) and enumerates the returned fields (bio, avatar, account counts, verification status). It explicitly distinguishes itself from soundcloud_search, soundcloud_user_tracks, and soundcloud_playlist, so an agent can route without opening any schema.

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?

Names three sibling tools and the condition each covers: soundcloud_search to find accounts, soundcloud_user_tracks for uploads, soundcloud_playlist for playlists. This is explicit when-to-use guidance with alternatives, leaving nothing to inference.

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