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

With no annotations, the description carries the full burden; it implies a read-only inventory view and clarifies that low_only is a threshold filter rather than a sort. It does not disclose whether archived items are included by default, pagination/limit behavior, or permission requirements.

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 sentences, no filler, and the core semantics of the filter are front-loaded immediately after the resource statement. Every clause adds information.

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 return-value explanation isn't required, and the description is adequate for a simple three-parameter list. It still leaves gaps an agent would want: default inclusion of archived records, result limits, and how this differs from the other stock/materials siblings.

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 the description must compensate. It meaningfully defines low_only ('at or below their low point'), but shop_id and include_archived get no treatment — the latter is guessable from its name but never confirmed as defaulting off or affecting counts.

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 states the resource (tracked materials) and what the response contains (count on hand, low point), which is enough to distinguish this list tool from sibling mutations like stock_adjust or stock_setLevel. The listing verb is only implicit ('Tracked materials'), and there's no explicit contrast with materials_list, but the inventory-level framing is clear.

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?

It explains the low_only flag's purpose in operational terms ('a reorder list'), which is a genuine usage cue for that path. However, there is no guidance on when to choose this over materials_list, stock_moves, or stock_adjust, and nothing about the default unfiltered behavior.

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