spotify_recently_played

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

Description notes result count up to 50 and chronological order, but does not disclose authentication requirements, rate limits, or return structure. Since no annotations, description carries full burden; adequate but sparse.

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?

Single sentence with no redundancy. Essential information front-loaded. Every word earns its place.

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?

Simple tool with one param and output schema present. Description covers core behavior but omits common details like authentication, implicit data scope (e.g., last 30 days), and output shape. Adequate for low complexity but incomplete.

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?

Parameter 'limit' has no schema description (0% coverage). Description adds value by mentioning 50 cap, but does not explicitly link to limit parameter. Basic compensation but could clarify parameter semantics.

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?

Description clearly states verb 'Get', resource 'your recently played tracks', order 'reverse chronological', and limit 'up to 50'. Distinguishes from siblings like 'get_saved_tracks' and 'now_playing'.

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. Does not mention that it returns current user's recently played, or that it's read-only. With many sibling tools, explicit usage context would be helpful.

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