lastfm_top_tracks

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

No annotations are provided, yet the description fails to disclose critical behavioral traits: how authentication works (api_key), how 'top' is defined, order of results, pagination, or error scenarios. This omits essential context for reliable invocation.

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 short sentence, which is concise. However, it sacrifices necessary detail, making it under-specified for an agent. It earns a middle score because it is efficiently structured but not suitably informative.

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?

Given the lack of output schema and annotations, the description should cover return format, error handling, and prerequisites. It does not, leaving the agent without enough context to use the tool correctly in a real scenario.

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?

With 0% schema description coverage, the description must clarify parameters but does not. It does not explain what 'limit' controls (e.g., max results) or the purpose of 'api_key' (likely a required authentication token). The agent has no semantic understanding of these inputs.

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 states the action ('Get top tracks'), the specific resource ('top tracks for an artist'), and the source platform ('on Last.fm'). This distinguishes it from sibling tools like 'lastfm_chart_top_tracks' and 'lastfm_artist_info', which serve different functions.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not explain that this fetches per-artist top tracks, as opposed to global charts, or mention any prerequisites or conditions for use.

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