get_recently_played

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

The description adds meaningful behavioral details beyond the readOnlyHint annotation: the 50-play Spotify cap, the ordering guarantee, the Unix ms timestamp format, and the mutual exclusivity of after_ms/before_ms. These are exactly the kind of constraints an agent needs to know.

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 compact and front-loaded: the core behavior appears first, followed by the critical cap/alternative warning, then the parameter note. Every sentence contributes necessary information without redundancy.

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 the main behavior, the key limitation, the relevant alternative, ordering, and parameter constraints. The output schema exists to describe return values, so the description does not need to repeat them. This is complete for safe and correct use.

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 0%, so the description must carry the semantic load. It explains the meaning and units of after_ms and before_ms and their mutual exclusivity, but does not explicitly describe the limit parameter beyond the schema default. This is strong but not fully complete.

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 returns the user's last-played tracks ordered most recent first, which is a specific resource and result. It also explicitly distinguishes itself from a full listening history, preventing confusion with the local analytics sibling tools.

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 explicitly tells agents when not to use this tool: it is not a full listening history, and the local analytics tools should be used for that instead. It also documents the mutually exclusive timestamp parameters, giving clear guidance for invoking it correctly.

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