recent_tracks

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Recently played' implies a read-only, recency-ordered list, but there is no mention of auth requirements, ordering, or whether results are scoped to the current user.

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 text is short but not concise in a useful sense: it is a bare fragment rather than a front-loaded sentence with an action and scope. It under-specifies rather than trimming waste.

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?

A one-parameter tool with no annotations and no output schema needs the description to explain operation, scoping, and limit behavior. A four-word fragment leaves every one of those gaps open.

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% and the single limit parameter is undocumented in both the schema and the description. No default, maximum, or meaning for limit is given, so the description fails to compensate for the coverage gap.

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 fragment names the resource (recently played tracks) but supplies no verb, so the agent must infer that it lists them. It is distinguishable from siblings like top_tracks or now_playing, but only because of the noun phrase, not because the description states the operation.

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?

There is no indication of when to use this rather than top_tracks, saved_tracks, or now_playing, nor any prerequisites or exclusions. The description provides no usage context at all.

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