Switch active SoundCloud account

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

Annotations already signal mutation, idempotency, and non-destructiveness. The description adds valuable behavioral context: the selection persists across sessions and affects subsequent tool calls, plus it returns the account list.

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?

Three short, purposeful sentences. The action is front-loaded, the behavioral consequence is explained, and the return value is noted with no 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?

For a one-parameter, non-destructive account-switching tool, the description covers the purpose, the effect on other tools, persistence, and return value. Nothing essential is missing for correct invocation.

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 single parameter is fully documented in the schema with 'Alias, username or user URN of a logged-in account.' The description adds little beyond restating that it selects among logged-in accounts, so the schema carries the semantic weight.

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 states a specific verb and resource: 'Make one of the logged-in accounts the active (default) one.' It also clarifies the effect on other tools, distinguishing it from auth_status, auth_login, and auth_logout.

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 gives clear context for when the tool matters: after switching, tools that take no account parameter and public reads will use this account. It does not explicitly name alternative auth tools or exclusions, but the intended usage is evident.

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