auto_refresh_spotify_token_if_needed

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'auto check and refresh if needed' without specifying what 'if needed' means (expiration, threshold), whether the refresh can fail, or what side effects occur (e.g., credential updates). It does not mention required secrets, idempotency, or error handling, so an agent has limited understanding of the tool's execution behavior.

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 sentence that identifies the action and resource without excess words. It is appropriately concise for a tool with no parameters, though the vague 'if needed' could be more precise without bloating the text.

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?

The tool has no output schema and no annotations, so the description is the only source of behavioral context. It fails to explain the triggering condition, the success/failure behavior, or any prerequisites like OAuth configuration, leaving an agent uncertain about when and how to safely invoke the tool. For a simple but conditional operation, this is a notable gap.

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 input schema has zero parameters, so there is nothing for the description to clarify beyond what the schema already shows. The description's explanation of the tool's conditional behavior is sufficient for a no-arg invocation, and per the baseline for 0 parameters, a 4 is appropriate.

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 a specific verb ('check and refresh') and resource ('Spotify access token'), and the conditional phrase 'if needed' hints at the auto-refresh behavior that distinguishes this from the sibling refresh_spotify_token. It is not a tautology and gives an agent a solid idea of the tool's purpose, though it does not explicitly name the sibling it differs from.

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?

There is no guidance on when to use this tool versus alternatives like refresh_spotify_token or get_spotify_token_status. The description implies a conditional refresh but does not state any preconditions, exclusions, or preferred contexts, leaving the agent to infer the usage policy.

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