Connect SoundCloud

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

The description discloses that opening a browser for OAuth and storing a token are side effects. Annotations already indicate openWorldHint=true and readOnlyHint=false, so the description adds useful context about the OAuth mechanism. No contradictions.

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, clear sentence that front-loads the purpose and efficiently conveys the entire tool behavior without unnecessary words.

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 tool with zero parameters and no output schema, the description is complete. It explains the login process, the side effect (opening browser), and the storage of the token for future sessions.

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?

There are no parameters in the input schema. The description provides the full meaning of the tool's operation, which is essential since the schema alone offers no information.

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 clearly states the action ('Log in'), the resource ('SoundCloud'), and the method ('opens a browser for OAuth and stores the token'). It distinguishes itself from sibling tools that perform other operations like adding tracks or signing out.

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 when to use this tool (before other SoundCloud operations) and provides context about the OAuth flow. However, it does not explicitly state when not to use it or mention alternatives like auth_status for checking login status.

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