get_user_weekly_artist_chart

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

Without annotations, the description carries full behavioral burden. It only discloses that omitting from/to yields the latest chart, but fails to mention ordering, limits, error conditions, or return format. The schema descriptions for from/to already cover their meaning, so the description adds minimal value.

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, front-loaded sentence of 14 words with no unnecessary words. It efficiently conveys the core purpose and the default behavior. Could be slightly more structured, but it is appropriately concise for a simple tool.

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 no output schema, the description should at least mention the return type (e.g., list of artists with play counts). It does not explain what constitutes an 'artist chart' or any pagination. For a chart tool, this missing information reduces completeness.

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 100%, so baseline is 3. The description adds 'for a given week (or the latest)', which complements the from/to parameters but does not add significant new meaning beyond what the schema descriptions already provide. No additional usage details are given.

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 verb 'Get' and resource 'user's artist chart', and adds nuance with 'for a given week (or the latest)'. It clearly differentiates from sibling tools like get_user_weekly_album_chart by specifying 'artist chart', though it does not explicitly contrast them.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., get_user_weekly_album_chart, get_user_weekly_track_chart). There is no mention of prerequisites or when not to use it, leaving the agent to infer from the tool name alone.

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