artist_genres_compact

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

With no annotations provided, the description carries the full disclosure burden. It adds genuinely useful behavior: the 50-ID batch cap, the single-call quota (️ one GET /artists?ids= call), and the two-column output shape. However, it is silent on edge-case behavior such as invalid or unknown IDs, duplicate ID handling, and ordering, which leaves meaningful gaps for a batch tool.

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 tight sentences with zero wasted words. The input→output contract is front-loaded in the first sentence, and the quota disclosure sits cleanly in the second. The arrow and emoji are compact scannability aids, not 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 low-complexity batch projection with 100% schema coverage and no output schema, the description supplies everything essential: input cap, output columns, and API cost. The remaining gaps — edge-case behavior and the exact rendering of the genres field in responses — are minor for this tool class. Slightly above the viable minimum.

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%: artist_ids documents its 50-ID cap and response_format documents each enum value's meaning. The description adds the output-side interpretation ('name·genres two-column projection') that connects artist_ids to its result, but parameter-level semantics are already fully carried by the schema, so the baseline 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?

The description states a precise contract: up to 50 artist IDs transform into a name·genres two-column projection. The phrase 'compact roster view over sever-al-artists' distinguishes it from the full-data sibling get_several_artists and the single-artist get_artists_genres, so an agent can tell this tool apart without opening their schemas.

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 'compact roster view' phrasing implies the intended use case (lightweight, name+genres-only lookup) and the quota note hints at efficiency as a selection factor, but no alternative tool is explicitly named and no when-not-to-use condition is stated. The agent must infer when to prefer this over get_several_artists or get_artists_genres.

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