spotify_get_recently_played

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

No annotations provided, so the description carries full burden. It does not disclose authentication requirements, rate limits, or whether the history is device-specific. It only states the operation, leaving the agent unaware of important behavioral traits like read-only nature or data freshness.

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 concise sentence that communicates the core purpose efficiently. No superfluous words, and it is front-loaded. Perfect for a simple getter tool.

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 no output schema and no annotations, the description is minimal but adequate for a straightforward read operation. However, it could be improved by mentioning the return format (e.g., list of track objects with timestamps) or pagination. Still, it covers the essential behavior.

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 only parameter 'limit' is fully described in the schema (max 50, default 20). The description adds no additional context beyond the schema. With 100% schema coverage, a baseline of 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 it retrieves tracks from recently played history. It distinguishes itself from sibling getter tools like spotify_get_current_track and spotify_get_saved_tracks by specifying 'recently played history.' However, it could be more explicit about the scope (e.g., time range or number of recent items).

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?

No guidelines on when to use this tool versus alternatives. The description does not mention when to prefer this over other track-related getters like spotify_get_current_track or spotify_get_saved_tracks. Context signals show many siblings, but no differentiation is provided.

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