deezer_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only implies a read-only search operation but does not mention authentication requirements, rate limits, pagination behavior, or any potential side effects. The description is too minimal to adequately inform the agent.

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 of six words, efficiently conveying the core action and target. It is front-loaded and contains no superfluous information, achieving maximum 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 absence of annotations, output schema, and the presence of sibling tools, the description is incomplete. It does not explain return values, pagination, or how to interpret results. The tool is simple, but a more complete description would include guidance on search behavior and result structure.

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 only one parameter with a description (type), and schema description coverage is low at 33%. The description lists the entity types ('tracks, artists, or albums') which loosely corresponds to the type parameter, but does not explain the purpose of the 'q' or 'limit' parameters. More elaboration on how to use these parameters would be needed.

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 the resource ('Deezer for tracks, artists, or albums'). It is specific about the entity types covered, which helps differentiate from sibling tools like deezer_search_playlist that focus on playlists. However, it does not explicitly differentiate from deezer_chart or deezer_get_* tools, but the verb and resource combination is clear.

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 such as deezer_get_album, deezer_get_artist, or deezer_search_playlist. There is no mention of prerequisites, context, or when not to use this tool.

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