spotify_status

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. It explains that the tool checks login status and shows the connected account, but it does not describe potential failure modes, network dependencies, or the exact format of the response. Basic behavior is clear, but richer context about side effects or preconditions is missing.

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 two sentences, front-loaded with the main purpose, and every word adds value. It avoids redundancy and effectively communicates the essential information in a compact form.

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 simplicity of the tool (no parameters, no output schema, no annotations), the description provides sufficient context: it states what the tool does, what it reveals, and when to call it. While a more detailed return value description could be added, it is not necessary for an agent to understand and correctly invoke this straightforward status check.

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, so the schema is fully comprehensive. The description correctly avoids describing any parameters, and with 0 parameters, a baseline score of 4 is appropriate since there is no need for additional parameter explanation.

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 'Check Spotify authentication status' with a specific verb and resource, and it explicitly distinguishes itself by showing login state and connected account. It is distinct from sibling tools like spotify_auth and spotify_logout, making its purpose unambiguous.

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 gives an explicit directive to 'Call this first before using other tools,' providing clear when-to-use guidance. However, it does not explicitly mention when not to use it or contrast it with alternative authentication tools like spotify_auth, though the context makes this implied.

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