spotify_playlist_freshness

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

With no annotations, the description carries full burden. It implies a read operation ('scan', 'show') but does not explicitly state safety, authentication needs, or data scope beyond scrolling. The sorting behavior is mentioned, which adds some value.

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, 17 words, front-loaded with the main action. Every word is essential and adds value. Excellent conciseness.

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?

While output schema is present, the description omits parameter explanations and lacks details about the tool's scope. For a tool with two parameters and a specific use case, more contextual guidance would improve completeness.

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 coverage is 0%, but the description does not explain either the 'owner_only' or 'limit' parameters. It only says 'scan all your playlists', which conflicts with the default filtering. No parameter semantics are provided.

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 it scans playlists and shows last updated time sorted by staleness, which is a specific verb+resource combination. This purpose is distinct from sibling tools like spotify_playlist_analysis or spotify_playlist_compare.

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?

Implicitly suggests use when wanting an overview of playlist recency. Does not explicitly state when not to use or suggest alternatives, but the context is clear enough for an AI agent to infer its utility.

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