stock_low_stock

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

The readOnlyHint annotation already marks this as a safe read operation. The description adds useful behavioral context beyond that: the result set is based on stock-tracked items and a specific reorder threshold, and an empty result is a valid outcome, not an error. This helps an agent avoid misinterpreting a successful empty list as a failure.

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 entire description is a single compact sentence. It front-loads the core selection criterion and ends with a valuable interpretive note about empty results. Every word contributes meaningful information with 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 simple read-only list tool with one required parameter, the description covers the essential selection logic and the meaningful empty-result behavior. It does not describe the response shape, but with no output schema present, this is a minor gap. Some potential overlap with sibling low-stock tools is not addressed.

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?

The schema has only workspaceId with no description, and the description text does not mention workspaceId at all. With 0% schema description coverage, the description should compensate but offers no parameter-level meaning, leaving the agent to infer that workspaceId identifies the workspace context.

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 clearly identifies a specific resource and filter condition: stock-tracked items whose total on-hand is at or below their D00 reorder point. It reads as a noun phrase rather than an explicit imperative like 'List' or 'Retrieve,' but the intent is unambiguous. It does not differentiate from the closely named sibling inventory_low_stock, so it loses the last point.

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?

No guidance is given about when to use this tool versus alternatives such as inventory_low_stock, inventory_reorder_candidates, or stock_on_hand. The statement 'Empty is not an error' hints at how to interpret results but provides no selection context or exclusions.

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