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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no additional behavioral details such as rate limits, auth requirements, or response quirks. Since annotations carry the burden and the description is consistent, a neutral 3 is appropriate.

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 concise sentence: 'Get a SoundCloud profile by handle.' All words are relevant, and it is front-loaded with the action and resource. There is no redundancy or filler.

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?

There is no output schema, so the description should explain what the profile contains or what the response looks like. It does not. An agent may not know whether the profile returns basic info (name, URL) or detailed stats. This is a notable gap for a tool that returns data without schema guidance.

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?

The schema descriptions cover 100% of parameters. The handle parameter is described as 'SoundCloud handle to look up, with or without a leading @', which is clear. The description merely restates 'by handle' without adding new meaning, so it matches the baseline of 3.

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 the specific verb 'Get' and the resource 'SoundCloud profile' with the method 'by handle'. This clearly distinguishes it from sibling tools like soundcloud_profile_tracks_list and soundcloud_track_get, which deal with tracks. The purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to prefer this over other profile getters (e.g., instagram_profile_get) or when to use the track-related SoundCloud tools. There is no implicit or explicit context beyond the tool name itself, so an agent receives no routing assistance.

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