artist_catalog_stats

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

The description explicitly discloses that the tool performs exactly one paginated /artists/{id}/albums walk and consumes one quota, which is valuable behavioral and cost context. It does not explicitly say 'read-only' or describe output formatting, but 'Numbers-only catalog profile' and the absence of mutation language make side effects unlikely.

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 two sentences with no fluff; the metric list is dense and front-loaded. There is minor redundancy between 'from one paginated discography walk' and the quota sentence's 'one paginated /artists/{id}/albums walk'.

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?

The enumerated metrics make the return value reasonably clear even without an output schema, and the quota disclosure aids cost planning. However, the description does not differentiate from the near-duplicate artist_discography_stats sibling, nor does it clarify pagination depth or edge cases, leaving tool selection somewhat ambiguous.

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 coverage is 100%, so the schema already documents artist_id, include_groups, and response_format. The description's mention of 'release totals by group' loosely aligns with include_groups but adds no parameter-level detail beyond what the schema provides.

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 the tool's output as a numbers-only catalog profile and enumerates concrete metrics (release totals by group, summed track counts, average tracks, active span, busiest year, median release gap), making the function clear. However, it does not distinguish itself from the near-identically named sibling artist_discography_stats, so the description alone does not let an agent tell them apart.

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?

No when-to-use or alternative guidance is given. The quota and 'one paginated walk' hint at cost-aware usage, but the description never states when to prefer this tool over artist_discography_stats or artist_discography_timeline.

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