refresh_box_sets_cache

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

With no annotations, the description carries the full burden. It discloses the network fetch, caching side effect, filtering rule, required DISCOGS_TOKEN, and return summary. It does not explain overwrite/destructive behavior or rate limits, but it covers the key behavioral traits for using the tool safely.

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 well-structured into purpose, filtering/exclusion/token note, and return summary. Every sentence adds useful information with no fluff or repetition, and the key purpose is front-loaded.

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 description covers the tool's purpose, filtering, exclusion, auth requirement, and return output despite no output schema. It falls short only in not explaining the force parameter, which is a meaningful gap for correct invocation.

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 0%, and the description does not compensate. It mentions the artist context but never explains the force parameter or the roles of artist_mbid/discogs_artist_id beyond what the schema names imply. 'force' is left completely ambiguous.

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 specific action: fetch King Crimson's compilations/box sets from Discogs and cache their tracklists for use by song_box_sets. It clearly distinguishes from siblings like song_live_releases and refresh_live_releases_cache by scoping to Main-role compilations/box sets.

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?

It explicitly says this refresh supports song_box_sets lookups and excludes single-show live downloads, which are covered by song_live_releases. This provides both a clear when-to-use and an explicit alternative, making the usage context strong.

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