lastfm_search_artists

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

No annotations are provided, so the description should disclose behavioral traits like rate limits, authentication requirements (api_key parameter), or result behavior (e.g., max results). The single sentence provides none of this, leaving the agent blind to important constraints.

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 extremely concise (one sentence, 4 words), but it lacks necessary details for a functional tool. It is front-loaded with the action word, but the brevity comes at the cost of completeness. Could be expanded without losing conciseness.

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 presence of parameters and no output schema, the description should explain what the search returns (e.g., a list of artists with basic info). Without this, and with no behavioral context, the tool is incomplete for an agent to use effectively.

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%, and the description adds no information about the parameters. While 'artist' is self-explanatory, 'limit' and 'api_key' are not described in either the schema or the description, forcing the agent to rely on inference.

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 'Search for artists on Last.fm' clearly indicates the action (search) and resource (artists on Last.fm). Among siblings like lastfm_artist_info and lastfm_similar_artists, the term 'search' distinguishes it as a general lookup, though it doesn't specify the result structure.

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 provided on when to use this tool versus alternatives. Siblings like lastfm_artist_info exist for specific artist details, but the description does not clarify that this tool is for broad searches while others are for detailed info. Implicit distinction is insufficient.

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