generate_shopping_list

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

The description discloses that the output is deterministic and not LLM-generated, and that leftover nights add nothing. However, it does not mention potential error states (e.g., no current plan) or output format, and no annotations are provided.

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 long, front-loaded with the core purpose, and every sentence adds value without redundancy.

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?

The description covers the tool's core functionality and behavioral traits adequately for a parameterless tool. It does not explain prerequisites like having a plan, but that is implied by 'current plan' and sibling tool context.

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?

There are no parameters, and schema coverage is 100%. The baseline for zero parameters is 4, and the description does not need to add parameter info.

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 that the tool generates a consolidated shopping list for the current plan, merging and scaling ingredients across cook days. It distinguishes itself from sibling tools that deal with recipes, planning, or exporting.

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 implies usage after planning is done, but lacks explicit when-to-use or when-not-to-use guidance or alternatives. The context suggests it is used when a shopping list is needed, which is reasonably clear.

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