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

The description adds behavioral details beyond annotations, such as setting qty to 0 to remove the line. Although annotations mark destructiveHint=false, the description clarifies that removal is possible. It also conveys that index comes from view_cart.

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 highly concise: one sentence with a colon and then the parameter list. Every word is necessary and no repetition.

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 covers the main use cases (changing qty, size, fabric, removal). An output schema exists, so return values are documented separately. It could mention availability constraints for size and fabric, but those are in the schema.

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?

All four parameters are described in the schema (100% coverage), so the description adds no new semantic meaning beyond listing the parameters. The note about qty=0 is already in the schema description.

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 the verb 'Change' and the resource 'a cart line', specifying identification by index from view_cart. It distinguishes itself from siblings like add_to_cart, cart_remove, and set_cart_quantity by covering quantity, size, and fabric updates in one tool.

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 context ('from view_cart') and mentions that setting qty to 0 removes the line, implying when to use removal. However, it does not explicitly state when not to use this tool or point to alternatives for adding or removing entirely.

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