Discogs: add release to collection

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and does not mention authentication requirements, duplicate handling, side effects, or the response format. This is a mutation tool, so such details are important.

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 a single sentence with no filler or redundancy. It is extremely concise and front-loaded, earning a perfect score for conciseness.

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 tool has no output schema and no annotations, so the description should cover prerequisites, side effects, and return behavior. It only states the core action, leaving the agent to infer authentication requirements, duplicate handling, and expected outcomes. The simplicity of the operation mitigates this slightly, but important context is missing.

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 coverage is 50% (folder_id is described, release_id is only typed). The description adds implicit meaning by mapping 'release' to release_id and 'collection folder' to folder_id, but it does not explain optionality or defaults beyond the schema. It partially compensates but not fully.

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 ('Add') and resource ('release to collection folder'), making the tool's purpose immediately clear. It distinguishes itself from sibling tools like discogs_remove_from_collection and discogs_add_to_wantlist by specifying the exact target.

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 guidance is provided on when to use this tool versus alternatives, nor are prerequisites or exclusions mentioned. There is no indication that the operation applies to the authenticated user's collection or any constraints such as existing folder ownership.

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