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

Annotations only flag destructiveHint=true; the description adds far more: choices are a full replacement with omitted entries DELETED, renaming is safe but choice replacement can be refused with an explanation, and ids must be preserved to keep prices and till history attached. This is exactly the extra context a destructive tool needs.

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-loads the destructive replacement warning, then layers prerequisites, the safer alternative, immutability, and refusal behavior in tight sentences. Every sentence carries actionable information; no filler.

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 destructive mutation with no output schema and full schema coverage, the description supplies the warnings, prerequisites, immutable-field limits, and refusal behavior an agent needs to call it safely. Nothing material is missing.

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 baseline is 3, but the description adds genuine meaning beyond the schema — it explains why choiceId must be kept (prices and till history stay attached) and clarifies replacement semantics for the choices array. The name uniqueness and immutability constraints are covered largely by the schema.

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 first sentence states a specific verb and resource ('Rename a modifier and/or REPLACE its whole choice list') and precisely delineates scope. It is immediately distinguishable from siblings like hub_update_modifier_choice, hub_create_modifier, and hub_delete_modifier_choice.

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: use update_modifier_choice for single-choice edits because it is 'safer and cannot drop the others', and read get_modifier first before sending the complete set. It also states what cannot be done (selectionType/allowQuantity) and that such cases require creating fresh.

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