search_artists

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

With no annotations, the description must carry the behavioral burden. It adds a GET endpoint and quota signal ('🟢 single'), implying a cheap read-only call, but it does not explicitly state auth needs, side effects, or output 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?

Two short, front-loaded fragments: the core purpose and endpoint come first, followed by quota. Every part earns its place and there is no filler.

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 search tool with full parameter documentation, the description supplies the differentiator ('artists only'), the exact endpoint, and quota. The lack of an output schema is partially mitigated by the response_format parameter's documented options, leaving only minor gaps around return shape.

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 100%, so the input schema already documents all seven parameters. The description adds no parameter-specific meaning beyond the artist-scoped endpoint, so the baseline score of 3 applies.

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?

States a precise action and scope: 'Search artists only' with the underlying GET /search?type=artist endpoint. This clearly distinguishes it from the general search tool and the other type-specific search siblings.

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?

'Artists only' gives a clear context and an exclusion: use this when the target is artist results, not other entity types. However, it does not explicitly name alternatives such as search or search_tracks for non-artist queries.

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