ghl_product_bulk_edit

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

Annotations already indicate write operation (readOnlyHint false) and non-idempotent. The description adds the 'max 30 entities' constraint and urges caution, but does not disclose failure behavior, atomicity, or side effects beyond editing. No contradiction with 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 concise with two main sentences plus endpoint info, but includes a redundant title phrase ('Bulk Edit Products and Prices'). It is front-loaded with the key action and constraint.

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 complex bulk operation with nested objects and no output schema, the description covers max entities and endpoint but lacks details on return values, error handling, or success criteria. The caution about scope is helpful but incomplete.

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% (all parameters have descriptions). The tool description does not provide additional meaning beyond what is already in the schema (e.g., altId, altType, products). Baseline 3 applies.

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 clearly states it performs bulk edits on multiple products and their prices, with a max of 30 entities. This differentiates it from single product tools (ghl_product_update, ghl_product_create) and sibling bulk tools (ghl_product_bulk_update) by specifying the scope and adding a caution about target scope.

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 warns to 'review the target scope carefully' and notes a max of 30 entities, but does not explicitly compare with alternative tools (e.g., ghl_product_bulk_update, ghl_product_update). It lacks when-to-use vs when-not-to-use guidance for an agent to choose optimally among siblings.

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