products_update_product_collection

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

Annotations already indicate this is a non-read-only, non-destructive, idempotent mutation, so the description carries a lower burden. However, it adds no extra behavioral context beyond what annotations state—it doesn't explain whether updates are partial or full replacements, whether fields not specified are preserved, or any side effects. Without such detail, the description offers minimal value in predicting behavior.

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—a single sentence with no fluff—which is good for front-loading. However, it's so sparse that it offers almost no information beyond the name, so it's not earning its place as a useful description. It's appropriately sized in terms of brevity but fails to convey any actionable guidance, making it average in conciseness-structure.

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?

This is a mutation tool with 7 parameters and no output schema, and it operates on an existing resource. The description provides no explanation of update semantics, required vs optional fields, or any constraints (e.g., whether slug changes are allowed). While annotations cover safety, they don't cover operational context. The description is incomplete for an agent to understand what fields can be changed and under what conditions, leaving significant gaps.

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 100%, meaning all seven parameters are documented in the schema itself. The description adds no additional meaning about parameters—it doesn't highlight required vs optional fields, relationships, or usage hints. Since the schema fully explains parameters, a score of 3 (baseline) is appropriate; the description neither helps nor harms parameter understanding.

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 states a clear verb ('Update') and resource ('Product Collection'), so an agent knows the basic function. However, it doesn't differentiate from siblings like products_create_product_collection or products_get_product_collection beyond the action verb, and it omits any mention of which fields can be updated. It's clear enough for a basic read of purpose, but lacks specificity.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention that a collection ID is required (though schema makes it required), nor does it state any conditions like 'use when you have an existing collection ID' or contrast with creation/deletion. The description provides zero context for when this should be invoked, leaving the agent to infer based on the name alone.

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