add_missing_to_shopping_list

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

With no annotations, the description carries the disclosure burden itself. It reveals a non-obvious behavioral trait: products without min_stock are silently ignored, so the operation may be incomplete in instances where few minimums are set. It doesn't specify duplicate handling or return behavior, but the key limitations are covered.

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 three sentences and front-loads the primary action before adding context. The limitation and fallback in the second paragraph both earn their place; there is 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 zero-parameter, no-output-schema tool, the description explains what it does, its blind spot, and the recommended alternative. The lack of return-value documentation is not a meaningful gap for an action that appends to a shopping list.

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 zero parameters and 100% coverage, so there is no parameter semantics for the description to clarify. Per the 0-parameter baseline, this dimension is effectively a non-issue.

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 first sentence states the specific action ('Add everything below its minimum stock level') and the target resource ('the shopping list'), making it clearly distinct from siblings like below_min_stock and add_to_shopping_list. The reference to Grocy's 'add missing products' adds useful context without obscuring what the tool does.

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?

The description explicitly names a limitation—only products with a min_stock set are considered—and gives a conditional alternative: 'read out_of_stock and add what's wanted by name instead' when few products have minimums. This is clear when-to-use vs when-not-to-use guidance.

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