Discogs: list label releases

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

The readOnlyHint annotation aligns with the 'List' operation, and no side-effect warnings are needed. The description adds label scoping but no additional behavioral context such as pagination behavior or rate limits.

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, front-loaded sentence with no unnecessary words or redundancy.

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 simple read-only list tool with pagination params in the schema and no output schema, the description adequately conveys the primary purpose. It doesn't describe return structure, but that's not essential for this low-complexity tool.

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 covers page and per_page with descriptions; label_id lacks description but is obvious from the tool's purpose. The description does not directly elaborate on parameters, so it adds little 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 clearly states 'List releases put out on a record label', using a specific verb and resource. It distinguishes from sibling tools like discogs_get_label (label details) and discogs_get_artist_releases (artist-specific list).

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?

Usage is implied by the description—use this tool to list releases for a label. However, there is no explicit guidance on when to use it over alternatives like discogs_get_label or discogs_get_artist_releases.

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