artist_top_vs_saved

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

With no annotations provided, the description carries the full burden and does well: it explicitly declares 'Read-only', states that no popularity fields are used (clarifying what the tool does NOT compute), and discloses the quota cost ('1 /me/top/artists + 2 capped library walks'). This goes beyond a typical description by revealing data sources and resource footprint, though it does not address edge-case behavior such as empty libraries or zero saved items.

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?

Three tight sentences with zero waste: first sentence delivers the core function, second adds the safety profile, third adds operational cost. The most important content is front-loaded, and each sentence earns its place without repetition.

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 read-only comparison tool with no output schema and a fully-documented input schema, the description covers the computation, the output ordering, the safety profile, and the quota. It does not elaborate on the return format (beyond the response_format param) or edge cases like empty results, but the core contract an agent needs to invoke and interpret results is present.

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 five parameters (window, artists_cap, response_format, saved_album_cap, saved_track_cap) are already documented. The description adds minimal param-level meaning — the phrase 'capped library walks' contextualizes the two caps, and 'top artists' links to artists_cap/window — but it does not meaningfully extend the schema's own documentation. 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 uses a specific verb ('compares') with a clear resource ('top artists from /me/top/artists' vs 'your own library') and states the exact output: saved-album and saved-track counts per top artist, ranked by library presence. This distinguishes it from siblings like get_top_artists (plain retrieval), saved_vs_playlist_coverage (playlist comparison), and artist_representation_census (census-style analysis).

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 gives implied usage context — it computes library-presence ranking of top artists and is explicitly read-only with a stated quota — but it never names alternatives or conditions for when to choose this over adjacent tools like top_artists_by_range, saved_vs_playlist_coverage, or library_coverage_report. There are no when/when-not statements, so an agent must infer the selection criteria.

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