getAccessToken

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

The description discloses a key side effect: updating spotify-config.json, which is beyond what the tool's name implies. However, with no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention error handling, token expiry behavior, or whether user interaction is required, making it only partially transparent.

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 sentence that is efficiently structured and front-loaded with the primary action. It contains no filler or redundant information; every word contributes to understanding the tool's purpose and side effect.

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?

There is no output schema, so the description should clarify what the tool returns. It mentions fetching tokens but does not state whether they are returned to the caller or only written to the config file. This ambiguity is significant for an authentication tool that likely feeds into other operations. The description is incomplete for agent decision-making.

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 the schema description coverage is 100%. The description clarifies that credentials are sourced from spotify-config.json, which explains why no parameters are needed. This adds meaning beyond the empty schema, aligning with the baseline of 4 for no-parameter tools.

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 the tool's function: fetching a valid Spotify access token and refresh token using credentials from spotify-config.json, and updating that file. It uses a specific verb ('fetches') and resource ('Spotify access token', 'spotify-config.json'), distinguishing it from sibling tools like refreshAccessToken which focus on refreshing an existing 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?

No guidance is provided on when to use this tool versus alternatives such as refreshAccessToken. It does not specify whether this is for initial authentication, re-authentication after expiry, or setup. The description lacks any explicit context or exclusion criteria, leaving the agent to infer usage.

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