refresh_spotify_token

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without explaining side effects, whether a refresh token must already exist, what happens on failure, or what the tool returns. That is a meaningful gap for a mutation-like auth operation.

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 front-loaded, active sentence with no filler or redundant information. Every word contributes meaning.

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 zero-input tool this is minimally viable: an agent knows what action to invoke. However, with no output schema and no annotations, the description omits useful context such as OAuth prerequisites, possible errors, and whether this operation updates the stored token credentials.

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 tool has zero parameters and an empty properties object, so there are no parameter semantics to document. The baseline for 0-parameter tools is 4, and the description appropriately focuses on the action itself rather than inventing parameter guidance.

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 a specific verb ('refresh') with a clear resource ('Spotify access token'). The word 'Manually' differentiates it from sibling auto_refresh_spotify_token_if_needed, and 'Spotify' distinguishes it from refresh_youtube_token and refresh_reddit_token.

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 word 'Manually' implies a deliberate, on-demand refresh rather than the automatic refresh path, but the description does not explicitly state when to choose this over auto_refresh_spotify_token_if_needed or mention prerequisites like completed OAuth setup. The usage context is implied rather than stated.

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