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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds genuinely useful nuance: the platform unsyncs the collection from sales channels first, and member products survive while only the grouping is destroyed. This clarifies the blast radius beyond the binary destructive flag, though it does not address permissions or reversibility.

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?

Front-loaded with the destructive verb and two tight sentences that each add value about side effects. The trailing '[#afdbfe]' token is stray markup that earns no place in the description.

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?

There is no output schema, but the description adequately covers the key behavioral consequence an agent must know before a destructive call (channel unsync, products preserved). It falls short on parameter meaning and permission/reversibility concerns, leaving the 0%-covered schema unassisted.

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% across 3 parameters, so the description carries the full burden and adds almost nothing: it never explains store_uuid, collection_uuid, or the optional workspace parameter. Only the singular 'a collection' hints that one collection is targeted, which the schema already implies via required UUIDs.

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+resource ('Delete a collection') and immediately clarifies scope by distinguishing what is removed (the grouping) from what is not (member products). An agent can distinguish it from delete_product, delete_design, and delete_workspace without opening any schema.

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 explains cascading behavior but never says when to use deletion versus alternatives such as archive or unsync_from_channel, nor does it name any sibling tool. No prerequisites or exclusions are stated.

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