bos_inventory_low_stock

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

No annotations provided, and the description only says 'Get products with low stock alerts' without disclosing behavioral traits like pagination, default threshold, or whether it returns alerts or actual stock levels.

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 description is only 4 words, which is underspecified rather than concise. It sacrifices clarity for brevity and lacks structure.

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?

Given the single undocumented parameter and no output schema or annotations, the description fails to convey return format, default behavior, or how low stock is determined. It is insufficient for correct tool usage.

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 input schema has one parameter 'threshold' (number, optional) with no description. The tool description does not mention or explain this parameter, leaving the agent to guess its purpose. Schema coverage is 0%.

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 states the tool returns products with low stock alerts, distinguishing it from inventory list or check tools. However, 'low stock alerts' is slightly ambiguous compared to specifying a threshold-based filter.

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 on when to use this tool versus siblings like bos_inventory_list or bos_smart_inventory_health. The description does not mention alternatives or specific use cases.

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