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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so overwrite and repeatability are structurally declared. The description reinforces this by stating the supplied number replaces the stored value and that previous and new quantities come back, but adds nothing about the optimistic-concurrency refusal path, which is the most consequential behavior here.

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?

Two tight sentences with the usage trigger front-loaded and the negative scoping last. Every clause carries information, though the return-value clause is partly redundant given an output schema exists.

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?

An output schema exists, so the description need not explain return values, and the concurrency guard and ID format are fully specified in the schema. What is missing is only the operational framing: that the item must first be read to obtain expectedLastEditTime and that a stale value yields a refusal.

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 every parameter's meaning, range, pattern and the lastEditTime conflict rule are already documented. The description restates the replace-vs-increment semantics already present in the quantity parameter's description, adding no new syntax or format detail; 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?

States a specific verb and resource ('correct or update how much of a stock item the salon has') and makes the set-not-increment semantics explicit ('the number given replaces the stored one'). It also rules out the adjacent operation ('Not for adding a new stock item'), so an agent can separate it from inventory creation without opening the 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?

Gives a clear triggering condition ('when someone asks to correct or update how much of a stock item the salon has') plus one exclusion. It does not state the prerequisite read (getting inventoryItemId and lastEditTime from list_inventory_items) or what to do when the update is refused, which the schema covers but the description does not.

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