get_recently_played

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

No annotations are present, so the description must disclose behavioral traits. It only documents input parameters, omitting authentication requirements, rate limits, or behavior when no tracks exist. There is no explanation of the return structure, despite an output schema existing.

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 front-loaded with a clear purpose sentence, followed by a structured parameter list. It is concise and well-organized, though it could be slightly shorter by omitting the 'Args' label since it's a docstring format.

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 output schema exists, the description need not detail return values. However, it lacks context about ordering, pagination, or typical use cases. For a simple list tool with three parameters, it is adequate but not fully enlightening.

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 description adds significant meaning beyond the schema: it specifies limit range (1-50), unit for after/before (Unix-ms cursor), and the constraint that only one cursor can be set. Schema descriptions are absent (0% coverage), so the description fully compensates.

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 'Get the user's recently played tracks,' which is specific and uses a verb-object structure. It distinguishes from siblings like 'get_currently_playing' by focusing on history, but does not explicitly contrast with other getters.

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?

Parameter descriptions provide usage hints (e.g., limit range, mutual exclusivity of after/before), but there is no explicit guidance on when to use this tool versus alternatives like get_tracks or get_playlist_items.

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