getRecentlyPlayed

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

No annotations are provided, so the description carries the full burden. It doesn't disclose authentication requirements (user-scoped data), pagination behavior, default limit when none is specified, or what fields the returned tracks contain. It only states what is fetched, not how it behaves.

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 is appropriately sized and front-loaded. No wasted words, though it could be slightly more informative without becoming verbose.

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?

Complete for basic invocation, but as a read tool with no annotations and no output schema, the description should clarify authentication scope, default limit, and output shape. It leaves several gaps for an agent to infer.

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 coverage is 100% – the single 'limit' parameter is fully documented in the schema with type, min, max, and description. Baseline 3 applies since the schema does the heavy lifting; the description adds no further parameter meaning.

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?

Clear verb+resource: 'Get a list of recently played tracks on Spotify'. Distinguishes itself from getNowPlaying (current track) and getTopTracks (most played over time), though it doesn't explicitly mention these siblings. The purpose is immediately clear.

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 guidance on when to use this tool versus alternatives like getNowPlaying or getTopTracks. The description provides no context about what 'recently played' means (time window, etc.) or when an agent should choose this over siblings.

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