spotify_auth

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

Annotations mark it as non-read-only and open-world, and the description corroborates by detailing external browser interaction, redirect to callback, automatic linking completion, and a visible success/failure page. This adds meaningful behavioral context beyond what the annotations alone provide.

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?

Three sentences with no redundancy: the first states the core purpose, and the next two explain the flow and outcome. It is front-loaded and efficient.

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-parameter tool with no output schema, the description covers the return value (auth URL), the required user action, and the post-approval flow (redirect and automatic linking), which is sufficient for an agent to invoke and explain the tool correctly.

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 takes zero parameters and the schema description coverage is 100%, so there is nothing for the description to add. The baseline of 4 is appropriate given no parameters exist.

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?

Clearly identifies the action (start Spotify account linking) and the return value (an auth URL). It is unambiguous versus siblings like spotify_devices (device management) and spotify_callback (callback handling).

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 positions this as the entry point in the OAuth flow and explains the sequence that follows: browser sign-in, redirect to the callback URL, and automatic linking. It doesn't explicitly say when not to use it or list alternatives, but for a 0-param auth starter the context is sufficiently clear.

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