Low stock

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real domain context beyond that: only products with 'managed' stock qualify, meaning untracked inventory is excluded, and the effective threshold can be per-product rather than global. It says nothing about ordering, pagination, or what happens when many products qualify.

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?

A single front-loaded sentence with the resource first and the filter semantics in a parenthetical, with no filler. The nested parenthetical is slightly dense but every clause carries 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?

For a two-parameter read tool with no output schema, the description covers the core filter semantics but leaves both the pagination parameter and the return shape (fields, ordering, whether only managed products appear in ordering) unaddressed. It is adequate rather than complete.

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 carries the burden, and it does explain `threshold` meaningfully: it is only the fallback, since each product's own low-stock amount takes precedence. However, `per_page` is never mentioned and the interaction between pagination and the result set is left unclear, so the compensation is only partial.

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 names a specific resource ('Products') and a precise filter condition ('managed stock at or below a threshold'), so an agent knows this is a filtered product listing rather than an arbitrary query. It does not explicitly distinguish itself from the sibling list_products, leaving that inference to the name.

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?

There is no explicit when-to-use or when-not-to-use guidance, and the closest alternative, list_products, is never mentioned. The agent must infer that this is the narrow 'stock below threshold' variant of a product listing purely from the name and the filter phrase.

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