get_similar_artists

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

Annotations already declare the operation is readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds the observable ordering behavior ('most similar first') and the effect of the autocorrect parameter, but does not mention other behaviors like pagination or rate limits. This is adequate for such a simple read-only lookup.

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 compact: one clear sentence introducing the tool and a short Args list that covers every parameter without extraneous wording. Every sentence is necessary.

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 read-only, idempotent tool with an output schema, the description covers the essential aspects: purpose, how to identify the subject, and how to control the result. The output schema handles return-format details, so nothing critical is missing.

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?

Input schema descriptions are completely absent (0% coverage), so the description must compensate. All four parameters are explained: artist and mbid as alternatives, limit as an expected count, and autocorrect as a flag for typo correction. This fully makes up for the lack of schema-level documentation.

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 uses a specific verb ('Get') and resource ('similar artists') and adds the ordering detail 'most similar first', making the purpose unmistakable. It clearly stands apart from siblings like get_artist or get_artist_top_artists, which focus on different facets of an artist.

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 conveys the context of when to use this tool: when you need artists 'similar to this one'. It does not explicitly mention alternatives or exclusions, but the parameter note 'artist required unless mbid is given' gives an implicit necessity to choose one identifier path.

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