artist_complete_check

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

No annotations are provided, so the description carries the full burden, and it does disclose genuinely useful operational traits: a quota of 2 reads (artist albums + saved albums) and page-capping, which helps an agent budget API calls and anticipate truncation. However, 'page-capped' is left vague — no cap size or consequence for very large catalogs is given, and read-only status is only implied, never stated.

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 the core purpose front-loaded and the quota disclosure as a value-add. Minor redundancy: 'your saved albums' appears in the first sentence and again in the quota parenthetical, but overall there is no 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?

The core computation is clear, and the response_format enum in the schema covers output style choices despite the absence of an output schema. But with no return-shape guidance, no sibling differentiation, and the correctness implications of page-capping unexplained, an agent still lacks a few pieces needed to use it confidently in this crowded toolset.

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 all four parameters are already documented in the schema, setting the baseline at 3. The description adds only marginal semantic value: '2 reads (artist albums + your saved albums)' clarifies the underlying data sources, and the album/single/compilation breakdown hints at what include_singles controls, but no parameter gains meaning beyond the schema.

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 a concrete comparison task — the artist's full album list vs the user's saved albums, showing what's missing with an album/single/compilation breakdown. That is a specific resource-and-operation pairing. However, the huge sibling list contains near-twins (artist_completeness_score, artist_album_completeness, artist_collection_gaps, artist_discography_gaps), and nothing here distinguishes this tool from them.

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 guidance, no exclusions, and no named alternatives. Given the dense cluster of similarly named artist-completeness siblings, an agent receives zero routing help to decide between this tool, artist_completeness_score, artist_album_completeness, or artist_collection_gaps.

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