deezer_chart

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It fails to mention authentication requirements, rate limits, or output format. The minimal description gives no insight into how the tool behaves beyond its basic 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 very short and to the point, but it sacrifices useful detail for brevity. It is appropriately front-loaded but fails to include necessary information that could be provided without significant bloat.

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 that there is no output schema and low schema description coverage, the description should compensate with more detail. It does not explain the output format, pagination, or any default behavior, leaving the tool contextually incomplete.

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 (type, limit) with only 50% description coverage. The tool description adds no additional meaning beyond the schema, leaving the 'limit' parameter undocumented. The description does not clarify the valid values for 'type' beyond what is in the 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 the tool gets a Deezer chart listing top tracks, albums, or artists. It uses a specific verb and resource, and distinguishes from sibling tools like deezer_get_album or deezer_search. However, it doesn't explicitly state that it retrieves the global chart, which could add specificity.

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 alternative Deezer tools such as deezer_search or individual get tools. The description only indicates the purpose, leaving the agent to infer when a chart query is appropriate.

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