SoundCloud logout (remove account)

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

The description discloses the endpoint, token deletion, default/active-account behavior, all=true semantics, and the fact that public reads keep working. These details go well beyond the sparse annotations and give the agent a clear model of the tool's side effects.

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 three tightly packed sentences with no filler. It front-loads the core action, then addresses parameter behavior, then adds the public-reads note. Every sentence earns its place.

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 two-optional-parameter auth tool with no output schema, the description covers invocation semantics well: default account, all mode, and post-logout app-token behavior. It does not describe the response shape or error cases, but these are minor for this tool.

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 coverage is already 100%, so the baseline is 3. The description adds meaningful behavioral semantics beyond the schema by explaining what happens when account is omitted and what all=true does, which is valuable for correct invocation.

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 action ('Invalidate a stored user session (POST /sign-out)') and its consequence ('delete its tokens'), clearly identifying this as the logout tool. This distinguishes it from related auth siblings like login, status, and switch_account.

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 operational context: omitting account targets the active account, all=true removes every account, and public reads remain functional after logout. It does not explicitly name alternatives, but the usage behavior is unambiguous enough for an agent to select it appropriately.

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