genius_get_artist

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the action without mentioning any traits such as authentication needs (api_key is optional but not explained), error states, rate limits, or side effects. The absence of such detail leaves the agent underinformed.

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 sentence, which is brief and front-loaded, but it is too minimal. It could be more informative without losing conciseness, such as noting the source of the artist data or typical response content. It is adequately concise but under-specified.

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 there is no output schema, the description should at least hint at what is returned (e.g., artist details). It does not. Additionally, it lacks context on error handling, required authentication, or how the ID is used. The tool has only two parameters, but the description still feels 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?

Input schema has 0% description coverage, and the tool description adds no clarification beyond the field names. 'Get ... by ID' implies the 'id' parameter is used, but there is no explanation of 'api_key' or any constraints. The description fails to compensate for the lack of schema descriptions.

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 specifies a clear action ('Get') and resource ('Genius artist by ID'). It effectively distinguishes from sibling tools like 'genius_search', 'genius_get_song', and 'genius_artist_songs' by indicating a direct lookup by identifier.

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 offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, contexts, or situations where other tools might be more appropriate, leaving the agent to infer usage solely from the name and siblings.

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