ghl_product_bulk_update

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

The annotation destructiveHint is false, yet the description lists 'delete' as a possible operation, creating a direct contradiction. The description does disclose the destructive capability, but the rubric specifies a score of 1 when description contradicts annotations.

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 moderately concise but contains redundant phrasing ('Bulk Update Products' repeated) and mixes endpoint details with the functional description. It could be tightened without losing essential information.

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?

The description omits important context such as the required body structure, how to use filters, and the meaning of different 'type' values. For a complex mutation tool with no output schema, this leaves gaps in understanding how to correctly invoke it.

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 coverage is 100%, so the schema itself provides full descriptions for all parameters. The description adds no extra semantic meaning beyond listing operation types, resulting in a baseline score of 3.

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 starts with 'Bulk-mutates multiple products in one call', clearly stating the verb and resource. It enumerates specific operations (price, availability, collections, delete) and distinguishes from single-product tools like ghl_product_update, but does not explicitly differentiate from the similarly named ghl_product_bulk_edit sibling.

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 provides no guidance on when to use this tool versus alternatives such as ghl_product_bulk_edit or individual product updates. It only warns to review productIds and mentions OAuth scopes, but does not clarify prerequisites or situations where a different tool would be more appropriate.

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