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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds meaningful context beyond the annotations by enumerating exactly which fields come back and stating the batch limit of 50 artists, which is the key behavioral trait for planning calls. It does not mention rate limits or error handling, so it is not a 5.

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 with zero filler, front-loaded with what data is returned and ending with the batch scope. Every clause earns its place.

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?

With no output schema and a single simple parameter, the description does the necessary work by listing the metrics returned, so an agent knows what to expect. It does not describe response structure or ordering for multiple artists, which keeps it from a 5.

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 single 'artists' parameter's accepted formats and 1-50 range are already fully documented. The description only echoes the 'up to 50' limit and adds 'in one call', providing marginal value beyond the schema. Baseline 3 is appropriate.

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 names the exact resource (artists) and enumerates the specific metrics returned: monthly listeners, followers, world rank, popularity, genres, and top 5 cities with listener counts. It does not differentiate from close siblings like get_artist_overview or get_artist_insights, so it falls short of a 5.

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 phrase 'for up to 50 artists in one call' implies a batch use case, but there is no explicit guidance on when to use this versus get_artist_overview or get_artist_insights, and no stated exclusions or prerequisites. Usage is inferable but not spelled out.

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