deezer_search_playlist

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Search', which implies a read operation, but fails to mention authentication requirements, rate limits, result format, or any side effects. This is insufficient transparency for a tool with zero annotation coverage.

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 a single sentence with no extraneous information. It is concise and front-loaded. However, it may be too brief, missing potential value-added details that could be included without losing 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?

Given the tool's simplicity (two parameters, no output schema), the description is inadequate. It does not explain the scope of search (e.g., public playlists only?), return format, pagination, or how to interpret results. Siblings like deezer_search have similar brevity but this one needs more context to be fully usable.

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?

The input schema has two parameters (q and limit) with 0% description coverage. The description does not add any meaning beyond the schema, leaving the agent with no context about what q represents (e.g., query string) or what limit controls (e.g., number of results). This fails to compensate for the lack of schema descriptions.

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 is 'Search for Deezer playlists.' It clearly states the verb 'search' and the specific resource 'Deezer playlists', distinguishing it from sibling tools like deezer_search (which likely searches all content) and other deezer-specific tools. It is explicit and unambiguous.

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 are no guidelines on when to use this tool versus alternatives like deezer_search, nor any mention of when not to use it. The description implies usage through purpose but provides no contextual exclusions or guidance for the agent to choose between similar tools.

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