delete_folder

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

Annotations already declare destructiveHint=true, but the description adds the non-obvious behavioral requirement that both dry_run=false and confirm=true must be set together, plus the upstream API refusal on non-empty folders. That is exactly the context an agent needs to avoid a failed or unwanted destructive call.

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 short sentences, front-loaded with purpose and constraint, then the destructive precondition, then the API limitation. No filler and nothing buried.

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 destructive, no-output-schema tool, it covers purpose, safety preconditions, parameter interplay, and the API-side failure mode. Nothing an agent needs in order to call it correctly 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 description coverage is 0%, so the description must carry the load; it explains the semantics and required combination of both confirm and dry_run, which is the highest-risk ambiguity in the schema. folder_id is only hinted at ("not 0 or 1") and its format is never stated, leaving a small gap.

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?

States a specific verb and resource ("Delete an empty collection folder") and immediately scopes it away from the default folders via "not 0 or 1", which distinguishes it from create_folder and rename_folder among the siblings.

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?

Gives the preconditions that gate use: the folder must be empty, and the call only succeeds with dry_run=false AND confirm=true. It also gives the when-not condition (Discogs refuses folders containing items). It does not name an alternative tool, but no other sibling deletes folders, so none is needed.

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