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

Annotations declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, so the safety profile is already covered. The description adds genuine context beyond the annotations: partial-update semantics ('Only the arguments you set are changed') and that 'seo' replaces the entire existing SEO block. It stops short of explaining why the operation is flagged destructive, which keeps it at a 4 rather than 5.

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 purpose, then sibling routing, then a compact Args block. Nothing is padding, and the Args block is justified by the 0% schema description coverage rather than being redundant.

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?

With an output schema present, return values need no explanation, and annotations cover safety. Given 9 parameters at 0% coverage, the description is thorough; the only small gap is that the destructiveHint=true flag is not reconciled with the described behavior.

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 carries the full burden, and it delivers: every parameter gets meaning beyond its name, including the 'status: active or draft' value set and 'sort: New ordering weight. Leave -1 to keep current,' which explains the schema's -1 default.

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 ('Update a collection's own fields') and immediately scopes the boundary by naming what it does NOT cover (product membership). An agent can distinguish it from the add/remove/set_products siblings 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?

Explicitly routes the agent to the correct alternative for a closely related operation: 'To change which products it contains, use add_products_to_commerce_collection, remove_products_from_commerce_collection, or set_commerce_collection_products.' This is exactly the when-to-use-what guidance that distinguishes the tool from its closest siblings.

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