user_get_weekly_track_chart

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

Annotations already declare readOnlyHint=true, so safety is covered and the bar is lower. The description adds only that results carry play counts; it says nothing about pagination, ordering, empty-week behavior, or whether a username is required for private profiles.

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 no filler; the resource and scope come first and the default second. It is efficient, though the parenthetical could have been traded for genuinely useful routing or return-shape information.

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?

With four optional parameters, no output schema, and a simple read-only shape, the definition is minimally sufficient because the schema carries parameter meaning. It nonetheless omits return structure beyond 'play counts' and any indication of the week-range pairing constraint, which matters for this 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 all four parameters are already fully documented, including the LASTFM_USERNAME fallback and the unix-seconds sourcing for week_from/week_to. The description restates the default-week behavior but adds no new semantic detail, 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 ('weekly track chart'), a scope ('one specific week'), and a default ('most recent by default'), which is enough to separate it from siblings like user_get_weekly_artist_chart or user_get_weekly_album_chart. It stops short of explicitly naming those siblings, so it is clear but not sharply differentiated.

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?

There is no when-to-use or when-not-to-use guidance beyond the incidental note that the most recent week is the default. Nothing tells the agent that week_from/week_to values should come from user_get_weekly_chart_list, nor how this differs from user_get_top_tracks or user_get_recent_tracks; that sequencing only appears in the schema.

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