spotify_stop

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

No annotations are provided, so the description carries full burden. It states the action ('Stop playback') which implies a mutation/write operation, but doesn't disclose behavioral traits like whether this requires user authentication, what happens if no device is active, if it's reversible, or any rate limits. The description is minimal and lacks essential context for safe invocation.

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, clear sentence with no wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration, making it highly efficient and easy to parse.

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 tool's complexity (a mutation with no parameters) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication needs, error conditions, or what 'stop' entails (e.g., does it clear the queue?), leaving gaps that could hinder correct agent invocation.

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 0 parameters, and schema description coverage is 100% (though empty). The description doesn't need to add parameter semantics beyond what's in the schema, as there are no parameters to document. This meets the baseline for zero parameters, but doesn't provide extra value since there's nothing to compensate for.

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 action ('Stop playback') and target ('on the user's active device'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'spotify_play' (which would start playback) or 'spotify_current_track' (which would retrieve information), missing full sibling distinction.

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 context through 'on the user's active device,' suggesting this tool should be used when playback is active and needs stopping. However, it doesn't provide explicit guidance on when to use this versus alternatives (e.g., vs. pausing or other controls) or any exclusions, leaving usage somewhat implied rather than clearly defined.

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