user_get_weekly_album_chart

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavior context — results include play counts and the week defaults to the current one — but says nothing about ordering, pagination, or what an empty week returns. With no output schema, that return-shape context would have been valuable.

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 week scope come first, followed by the default and return content. It is efficient, though extremely terse for a tool with four parameters.

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?

For a read-only chart fetch with fully documented parameters and no output schema, the description covers what is returned (album entries with play counts) and the default week. It leaves minor gaps around ordering and empty results, which keeps it just short of fully complete.

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%, with all four parameters documented, including how week_from/week_to derive from user_get_weekly_chart_list and the limit bounds. The description only restates the 'most recent week' default already present in the schema, adding no new parameter meaning.

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: an album chart for exactly one week, including play counts. The word 'album' distinguishes it from user_get_weekly_track_chart and user_get_weekly_artist_chart, though it never names those siblings explicitly or contrasts with user_get_top_albums.

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?

'(most recent by default)' establishes the default behavior but gives no when-to-use guidance against alternatives such as the weekly track/artist variants or the top-albums tool. The routing hints about user_get_weekly_chart_list appear only inside the schema's parameter descriptions, not in the tool description.

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