Discogs: create marketplace listing

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

No annotations are provided, so the description must disclose behavioral traits itself. It explicitly states that the listing is 'real, publicly visible' and advises user confirmation, which is a significant caveat. However, it does not mention authentication requirements, side effects beyond visibility, or reversibility, though the warning partially compensates for this.

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 extremely concise, consisting of two short sentences. It front-loads the primary action and includes the essential warning without wasted words.

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?

Given the complexity (9 parameters, mutation, no output schema, no annotations), the description is too brief. It covers the core purpose and a critical caution, but omits details about parameters, return values, error scenarios, or prerequisites. The warning is helpful but not sufficient for a tool of this complexity.

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 only 44%, leaving several parameters (e.g., release_id, comments, allow_offers) without descriptions. The tool description does not mention or clarify any parameters, so it fails to compensate for the low schema coverage. It adds no value 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 the tool's purpose with a specific verb and resource: 'List a release for sale on the Discogs marketplace.' It also adds that the listing is 'real, publicly visible,' which distinguishes it from similar tools like update_listing or get_listing.

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 provides clear context for when to use the tool (creating a marketplace listing) and includes a strong practical guideline: 'confirm details with the user before calling.' It does not explicitly name alternatives, but the purpose is clear enough that an agent would not confuse it with update or delete operations.

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