statsfm_top_tracks_from_artist

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

With no annotations, the description must carry behavioral transparency. It does not state that this is a read-only lookup, mention whether it queries stats.fm or Spotify, or describe any side effects or errors. Only the noun phrase 'top tracks' implies a data return.

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 concise phrase with no filler. It is front-loaded with the key subject, though it is grammatically a noun phrase rather than a complete sentence.

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 simple lookup with a fully documented schema, the one-line description is mostly sufficient, but it does not describe the return shape or distinguish output variants (concise/detailed/json) beyond what the response_format parameter already implies. Given no output schema, a bit more context would help.

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?

The input schema already contains full descriptions for all 7 parameters, including defaults and enum meanings. The tool description adds no extra parameter context, so it meets but does not exceed the baseline for schema coverage.

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 identifies the resource (user's top tracks) and the filter (one artist), distinguishing it from sibling tools like statsfm_top_tracks_from_album. However, it lacks an explicit verb such as 'Retrieves', so it falls just short of a top score.

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?

No guidance is given about when to choose this tool over similar siblings (e.g., statsfm_top_tracks, artist_top_tracks, get_artist_top_tracks). The description only states what the tool returns, not the conditions or alternatives.

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