statsfm_charts_albums

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only chart operation, but it does not explicitly state that the tool has no side effects, that the target user's stats need to be public, or what data the movement indicators actually represent.

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 efficient sentence with the core intent front-loaded. It is not padded with trivia, though it is concise to the point of omitting useful usage or output context.

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?

This is a fairly simple, read-only chart tool with all schema fields documented, so the description is minimally sufficient for basic invocation. However, there is no output schema and the description does not define what the returned chart or movement indicators look like, which leaves some ambiguity for an agent choosing or parsing the result.

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 parameters are already well documented. The description adds light context by clarifying that the tool concerns a user's all-time album chart, but it does not add meaningful detail beyond the schema for parameters like limit, offset, max_results, or response_format.

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 identifies a specific resource (a user's all-time top albums) and a distinguishing feature (movement indicators), which helps separate it from similar siblings like statsfm_charts_tracks and statsfm_charts_artists. It lacks an explicit verb like 'list' or 'fetch', but 'chart of a user's top albums' is still readily interpretable.

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 guidance on when to use this tool versus alternatives such as statsfm_top_albums, statsfm_album_stats, or statsfm_charts_artists. The description implies usage through its wording but provides no exclusions, prerequisites, or alternative routing.

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