spotify_setup_instructions

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

No annotations are provided, so the description must disclose behavioral traits. It states that instructions are returned (read-only) but does not mention side effects, permissions, rate limits, or what the instructions contain. The description is minimal for a tool with no annotations.

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?

A single, clear sentence that front-loads the purpose without wasted words.

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 zero parameters, no output schema, and simple siblings, the description is adequate but lacks details such as prerequisites or the nature of the instructions. It could include hints about output format or steps covered.

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?

There are zero parameters, and schema description coverage is 100% (trivially). The description does not need to add parameter meaning beyond the schema, and its clarity suffices.

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 provides 'detailed setup instructions for authenticating the Spotify MCP server', specifying verb (get), resource (setup instructions), and purpose (authentication). It distinguishes from siblings like spotify_get_auth_status (status queries) and spotify_health_check (health checks).

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 implies usage when setup or authentication instructions are needed, but provides no explicit guidance on when to use this tool versus alternatives (e.g., after setup, use spotify_get_auth_status to verify). No when-not or alternative tool mentions.

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