auth-spotify

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

No annotations are provided, so the description carries full burden. 'Authenticate with Spotify' implies a state-changing operation (likely obtaining or refreshing tokens), but it doesn't disclose behavioral traits like whether it's interactive, requires user input, stores credentials, has side effects, or handles errors. This leaves critical gaps for an agent to understand how to invoke it safely.

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 extremely concise with just three words, front-loading the core action ('Authenticate') and target ('Spotify'). There's zero waste or redundancy, making it easy to parse quickly.

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?

Given the complexity of authentication (often involving tokens, scopes, or user interaction), no annotations, no output schema, and sibling tools that likely depend on auth, the description is incomplete. It doesn't explain what authentication entails, what it returns, or how it integrates with other tools, leaving significant gaps for an agent.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is given since the schema fully covers the absence of parameters, and the description doesn't need to compensate.

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 'Authenticate with Spotify' states the general purpose (authentication) and target service (Spotify), but it's vague about what authentication means in this context. It doesn't specify whether this initiates OAuth flow, validates existing tokens, or manages credentials, nor does it distinguish from other authentication-related operations that might exist.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing authentication before using other Spotify tools), timing considerations, or whether it's required for sibling tools like 'add-tracks-to-playlist' or 'search-spotify'. Without this, an agent might misuse it.

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