delete_collection

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only states 'Delete a collection' with no mention of permanence, cascading effects, authentication requirements, or error conditions. This is a destructive operation, yet the description fails to warn that deletion is irreversible or that it may fail if the collection is still published.

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, concise sentence that states the action and target. It is front-loaded and free of fluff, though it could be considered too sparse given the destructive nature and lack of behavioral details.

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 deletion tool with one parameter and no output schema, the description should at least mention irreversibility, prerequisites (e.g., needing to unpublish), or side effects. None are provided, making the description incomplete for an agent that must safely invoke deletion operations.

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?

The schema covers 100% of parameters with a description for 'id' including an example (e.g., 'gid://shopify/Collection/123456789'). The description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clear verb ('Delete') and resource ('collection'), making the primary action unambiguous. It distinguishes from siblings that operate on other resources (e.g., delete_product, delete_order), though it doesn't clarify which type of collection (smart vs. regular) is targeted.

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. It doesn't mention any preconditions (e.g., collection must be unpublished), restrictions, or contrast with sibling tools like create_collection or update_collection. The agent must infer usage solely from the tool name.

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