get_low_stock_items

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

With no annotations, the description carries the full burden. It reveals the operation is a read-only listing by using 'Lister', which implies no side effects, but it does not disclose additional behavioral traits such as sort order, inclusion of zero-stock vs. negative-stock, or handling of items without a minimum threshold. The description is minimally sufficient but not rich.

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 two sentences: the first defines the function, the second provides usage scenarios. Every sentence adds value with no redundancy or 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 zero-parameter list tool, the description covers the core purpose and common user intents. It lacks explicit return format or pagination details, but the absence of an output schema and the simplicity of the operation make this a minor gap; the use-case list adds practical completeness.

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 tool has zero parameters and the input schema is empty, so schema coverage is 100%. The description adds no parameter-specific information because there is nothing to document; baseline of 4 for zero-param tools is appropriate.

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 uses a specific verb ('Lister') with a clear resource ('tous les produits dont le stock est sous le seuil minimum de réapprovisionnement'), and it distinguishes itself from siblings like get_item_stock and get_expiring_items by defining a unique scope (items below reorder threshold).

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 explicitly states when to use the tool: 'Utiliser pour les alertes de réapprovisionnement, les rapports du matin, ou quand l'utilisateur demande...' and provides concrete example queries. It doesn't list exclusions or alternatives, but the when-to-use context is clear and actionable.

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