get_recently_played

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

With no annotations present, the description carries the full burden of behavioral disclosure, but it only supplies a noun phrase. It gives no hints about recency window, count limits, ordering, or whether the operation is a read. The elliptical phrasing could even be mistaken for a data label rather than an operation.

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 tiny, but this is under-specification rather than conciseness. It front-loads nothing meaningful beyond the tool name and has no structural benefit.

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 one parameter with no schema coverage, no output schema, and no annotations, the description fails to give the agent enough context to infer return shape, edge cases, or authentication implications. A single sentence with operational details would be a major improvement.

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 explain the limit parameter, but it says nothing about it. The agent has only the raw schema (default 50, max 50) and no clue what values mean for pagination or required behavior.

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 'Recently played tracks.' is essentially a tautology that restates the tool name. It contains no verb and never says what the operation does — list, fetch, return, etc. It also does nothing to distinguish this tool from siblings like get_playlist or get_top_tracks.

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 is provided on when to use this tool versus alternatives such as get_top_tracks or find_track. There is no mention of context, prerequisites, or exclusions. This leaves an agent to guess which tool fits the user's intent.

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