deezer_search

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Search Deezer' with no details on authentication, rate limits, pagination, or error handling. A search tool typically returns multiple results, but this is not confirmed.

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 wasted words. It is front-loaded with the action 'Search'. However, it misses opportunities to add structure (e.g., examples or parameter hints).

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?

The tool has no output schema and moderate parameter count. The description lacks any hint about the response format (e.g., list of results, metadata). It does not address the inconsistency with the 'type' parameter allowing playlists. Overall, it feels incomplete for a search tool.

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 33% (only the 'type' parameter has a description). The description lists 'tracks, artists, or albums' but the schema includes 'playlist' as an allowed value for 'type', creating an inconsistency. The 'q' and 'limit' parameters are undocumented in both the description and schema.

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 it searches Deezer for tracks, artists, or albums. It distinguishes from sibling tools like deezer_get_* (which retrieve specific items) and deezer_search_playlist (which only searches playlists). However, it does not explicitly exclude playlists, which the schema actually allows via the 'type' parameter.

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 on when to use this tool versus alternatives such as deezer_chart, deezer_get_album, or deezer_search_playlist. The agent must infer usage from sibling names alone.

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