SpotifyPlayback

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

No annotations are provided, but the description does not disclose side effects (e.g., pausing interrupts playback), prerequisites (e.g., active device), or error conditions. It only describes what each action does without deeper behavioral context.

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 concise with bullet points for actions, but it repeats the same information in the first paragraph and the schema's description field. It is mostly efficient but could be more streamlined.

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?

The description covers all actions and basic parameter usage, but lacks mention of prerequisites or error handling. For a tool with multiple actions and no output schema, it provides adequate but not deep completeness.

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?

Schema description coverage is 100%, and the tool description repeats parameter info (e.g., 'seek: jump to position_ms'). The description adds minimal extra meaning beyond the schema, so baseline 3 is appropriate.

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 manages playback with specific actions (get, start, pause, skip, previous, seek, volume), distinguishing it from siblings like SpotifyGetInfo and SpotifyQueue. Each action is briefly explained.

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 context for when to use each action (e.g., 'start: play spotify_uri, or resume if omitted'). However, it does not explicitly state when not to use the tool or mention alternatives like SpotifyQueue for queue management.

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