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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the substantive semantics: the value overwrites rather than increments, and the write targets an ItemShop record via a specific endpoint. That 'sets, does not add' warning is exactly the behavioral context an agent needs before a destructive write.

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 leading 'CHANGES STOCK COUNTS' hook front-loads the mutation, then each subsequent clause carries a distinct load: overwrite semantics, scale guidance, exclusion, identification options, endpoint. 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?

No output schema exists, yet nothing essential is missing for a 4-param destructive write: scope, overwrite behavior, valid identifier sources, and the shopID 0 pitfall are all covered. The remaining ambiguity (both IDs supplied) is minor.

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 baseline is 3; the description earns above that by explaining that shop identification is an either/or choice between shop_id and item_shop_id and where each comes from. It still doesn't state whether the two are mutually exclusive or which wins if both are supplied.

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 — 'sets (does not add to) the quantity on hand of one item in one shop' — with the crucial absolute-vs-increment distinction spelled out. This clearly separates it from siblings like update_item, which touches item attributes rather than per-shop stock.

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 usage: 'Use for correcting a few items; for many items use an inventory count in Lightspeed,' and gives a hard exclusion: 'Not for shopID 0 (the all-shops summary).' Both a preferred alternative and a when-not condition are present.

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