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

The description adds two facts not present in the annotations: the products:read permission requirement and the 'preview API may change without a version bump' stability warning. 'Read-only' merely restates readOnlyHint=true, but the auth scope and volatility disclaimer are genuine additions.

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 compact clauses, front-loaded with the 'Preview API' caveat and the core resource. Every clause carries information; the only redundancy is 'Read-only', which duplicates the annotation.

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?

With no output schema, the description usefully sketches the return ('one item and its pack balances') and states the auth scope. But for a tool whose two required parameters have zero schema documentation, it leaves an agent without the identifier semantics needed to construct a correct call.

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 0%, so both required parameters (locationId, colourBarItemId) rely entirely on the description for meaning, and the description mentions neither. It gives no indication of the loc_/cbi_ identifier formats, where to obtain the IDs, or whether location scoping affects results.

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-ish operation (retrieve one colour-bar stock item) with scope detail: 'and its pack balances; no personal recipes or mixes.' That scope boundary distinguishes it from the broader list/range siblings, though it never names an alternative explicitly.

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?

'Requires products:read' gives the prerequisite and the 'no personal recipes or mixes' clause signals what this endpoint will not return, which is real routing guidance. It stops short of naming when to call this versus cliento_list_colour_bar_items or cliento_get_colour_bar_range.

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