lastfm_get_artist_top_tracks

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

Annotations (readOnlyHint, destructiveHint) already indicate it's a safe read-only operation. The description adds no additional behavioral details (e.g., pagination behavior, API limits) beyond annotations, which is acceptable but not additive.

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, direct sentence with no unnecessary words. It is front-loaded and efficiently communicates the tool's purpose.

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?

The description is brief but, given the presence of an output schema and the tool's simplicity, it provides sufficient context for a basic understanding. However, it misses mentioning pagination or the need for exact artist names.

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 provides descriptions for all parameters (page, limit, artist), so schema description coverage is effective. The tool description does not add any parameter meaning beyond what the schema offers.

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 'Get the top tracks for an artist on Last.fm.' specifies a clear verb (Get), resource (top tracks for an artist), and context (Last.fm), differentiating it from siblings like lastfm_get_artist_info or lastfm_get_artist_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?

No explicit guidance on when to use this tool vs. alternatives such as lastfm_get_artist_top_albums or similar track tools. While the purpose is clear from the name, the description does not provide usage context or exclusion.

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