deezer_search_playlist

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

With no annotations, the description carries full responsibility for behavioral disclosure. It fails to mention any traits such as pagination (despite a 'limit' parameter), authentication requirements, rate limits, or output format. The description is essentially a bare statement of purpose.

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 extremely short (one sentence), which is concise but at the expense of necessary detail. It does not earn its place by providing value beyond the name; it essentially repeats the tool's name.

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 minimal schema, no annotations, and no output schema, the description is critically incomplete. It fails to specify return values, sorting, or any contextual detail that would help an agent use the tool effectively. A search tool requires more context about results.

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% (no descriptions for 'q' or 'limit'). The tool description does not explain what these parameters represent or how to use them, leaving the agent without guidance beyond the schema keys and types.

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 clearly states the action ('Search') and resource ('Deezer playlists'), making basic purpose unambiguous. However, it does not differentiate from the sibling tool 'deezer_search', which also performs searches but likely across all entities, missing an opportunity to clarify scope.

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 like 'deezer_search' or other Deezer tools. The description offers no context for selection, leaving the agent to infer usage solely from the name.

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