Repost / un-repost a track or playlist

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

Annotations already establish that this is a mutating, non-destructive, idempotent operation. The description adds useful behavioral context by specifying that it acts as the logged-in user and that the boolean controls whether the repost is added or removed. This goes beyond the structured annotations without contradicting them.

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 information-dense sentence with no filler. It front-loads the core action and boolean semantics, and the title reinforces the toggling behavior without redundancy.

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 four-parameter tool with complete schema coverage and no output schema, the description covers purpose, actor, and toggle behavior adequately. It does not explain edge cases like reposting an already-reposted item, but the idempotentHint annotation already signals that such calls are safe and idempotent.

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%, so the input schema already fully documents all four parameters. The description adds minor reinforcement about the reposted boolean and logged-in user scope, but no new parameter-level details such as examples, interaction between kind and target, or account resolution behavior.

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 identifies the action (repost or remove repost), the resource type (track or playlist), and the actor (logged-in user). It is immediately distinguishable from sibling tools like soundcloud_set_like, soundcloud_set_follow, and soundcloud_get_playlist_reposters.

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 makes the intended use evident: this is the tool for toggling a repost on a track or playlist. It does not explicitly name alternatives or exclusions, but there is no sibling tool that performs the same repost action, so the context is clear enough.

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