user_get_weekly_artist_chart

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

readOnlyHint=true already establishes the safe-read profile, so the bar is lower. The description adds the default-week behavior and mentions play counts are returned, but does not state ordering, whether the chart is ranked, or how an empty/invalid week pair is handled. The default-week information also duplicates the schema's own parameter descriptions.

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?

A single front-loaded sentence with zero waste: resource, scope, default, and return content in one pass. Nothing is redundant or padded.

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?

There is no output schema, so the description bears responsibility for conveying the return shape; "with play counts" gives a partial picture but omits ranking/ordering and per-entry fields. Calling the tool correctly is possible from the schema alone, but the result contract is only loosely described for a chart-listing 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 description coverage is 100%, so the four parameters are already fully documented, including the LASTFM_USERNAME fallback and the unix-seconds sourcing for week_from/week_to. The description adds nothing beyond echoing the most-recent-week default, so the baseline of 3 applies.

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 names a specific resource and scope: "artist chart for one specific week," which implicitly separates it from user_get_weekly_track_chart and user_get_weekly_album_chart by naming the entity type. It also states the return payload (play counts). It stops short of explicitly naming the sibling tools it differs from.

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?

Usage is only implied: "most recent by default" suggests calling with no arguments for a current snapshot, but there is no when-to-use versus when-not guidance and no mention that week_from/week_to values should be sourced from user_get_weekly_chart_list (that hint lives only in the schema). An agent must infer the workflow.

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