get_several_artists

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

With no annotations, the description carries full burden of behavioral disclosure. It mentions a batch limit but states 'up to 50 per request', whereas the ids schema says longer lists are fetched in chunks of 50 and merged — so the description understates actual behavior and may mislead an agent into rejecting longer inputs. It also omits that the tool makes multiple underlying calls and merges results, which matters for latency and rate limits.

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?

A single sentence that front-loads the action, resource, and key constraint with no filler. The parenthetical '(up to 50 per request)' adds the most operationally relevant detail without bloating the text.

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 tool with no output schema and no annotations, the description should at least clarify the chunking/merging behavior and what 'full details' means. The contradiction between the description's 'up to 50 per request' and the schema's chunked-merge behavior is a significant gap, and no guidance is given on choosing this over similar sibling tools.

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 baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides; the phrase 'by ID' merely echoes the ids field. It does not clarify max_results or response_format beyond their existing 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 states a specific verb ('Get'), resource ('detailed artist info by ID'), and batch scope ('several', 'up to 50 per request'). It distinguishes from sibling batch tools like get_several_tracks by naming the resource type and from get_artist by the plural/batch emphasis.

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 implies the main use case: retrieving details for multiple known artist IDs in one call. However, it gives no explicit when-to-use vs alternatives (e.g., get_artist for a single ID, get_artist_top_tracks for top tracks), and with dozens of artist-related siblings, some routing guidance would help. No exclusions or conditions are stated.

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