lastfm_artist_info

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds nothing beyond that: no indication of what fields are returned, whether a Last.fm API key is needed, or any rate-limit/auth behavior.

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 single sentence is economical and front-loaded, with no filler. But its brevity reflects under-specification rather than precision, so it is concise without being sufficiently 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?

With no output schema and 0% parameter description coverage, the description needs to carry more weight. It does not explain the return shape or the api_key parameter, leaving an agent with gaps before it can invoke the tool confidently.

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 0%, so the description must compensate. It says nothing about the required 'artist' parameter (name format, disambiguation) or the 'api_key' parameter, which is completely unexplained despite being a potentially critical auth input.

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 verb and resource are identifiable ('Get Last.fm artist info'), so an agent knows it retrieves artist data. However, it does not distinguish itself from adjacent siblings like lastfm_search_artists, lastfm_album_info, or lastfm_similar_artists, leaving the agent to infer the distinction from names alone.

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 instead of lastfm_search_artists or other Last.fm siblings. The description offers no prerequisites, no context about what 'artist info' covers, and no exclusions.

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