discogs_search_artists

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

With no annotations, the description should compensate but only says 'Search for artists on Discogs.' It omits critical details like result format, pagination, rate limits, or authentication requirements beyond the schema. The agent cannot infer the tool's behavior accurately.

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, concise sentence. While it avoids unnecessary words, it lacks structure and fails to provide enough detail. It is appropriately sized but sacrifices completeness.

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 tool is simple (2 params, no output schema), but the description is too skeletal. It does not explain the return value, how results are ordered, or any constraints. Given the lack of annotations, the description is incomplete.

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 coverage is 0%, so the description should explain the parameters. It does not, leaving 'q' and 'api_key' unexplained. The agent must guess that 'q' is a search query, and api_key is for authentication.

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 (Search) and resource (artists on Discogs). However, it does not differentiate from sibling tools like discogs_get_artist or discogs_search_releases, which could cause confusion about when to use this tool versus those.

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 over alternatives, such as discogs_get_artist for specific artists or discogs_search_releases for releases. The description lacks any context on prerequisites or typical use cases.

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