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

Annotations only declare readOnlyHint=true, so the description adds real value: it discloses strict owner scoping ('only ever the user's own playlists') and the fact that results feed the news Feed. It also documents the return payload since no output schema exists, though it says nothing about rate limits, result size, or what an empty list looks like.

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?

Front-loaded with the core purpose and the returned fields, then the call-first directive with the red-flag marker, then fallback branches. Slightly repetitive — 'the user's OWN feed playlists' and 'Owner-scoped — only ever the user's own playlists' say the same thing — but the density is justified for a routing-critical lookup.

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?

With no output schema, the description takes on the job of listing returned fields and does so, plus it supplies the ambiguity and empty-result handling the agent needs. For a zero-parameter read tool, nothing material is missing.

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?

Zero parameters, so the baseline is 4; the schema is an empty object and there is nothing for the description to clarify. The description instead spends its space on output fields and call-order rules, which is the right allocation for a no-param tool.

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?

States a specific verb and resource (list feed playlists), names the owner scope, and enumerates the returned fields (id, name, emoji, item_count, items[...]). The 'OWN' qualifier plus the 'drives their news Feed' note clearly separates it from create_playlist, add_to_playlist, and news_feed.

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?

Explicitly prescribes 'Call this FIRST whenever the user refers to a playlist BY NAME' and explains that the agent must fuzzy-match the spoken name against real names itself. It also covers both branches — ask which one when ambiguous, offer to create when the user owns none — so the agent knows when to use this versus create_playlist.

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