add_recipes_to_shopping_list

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

No annotations provided, so description carries full burden. It discloses ingredient merging and summing behavior, but lacks details on side effects (e.g., append vs. overwrite), permissions, or error handling. Partial transparency.

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?

Two sentences with no fluff. The first sentence is dense but covers core functionality. Slightly long but efficient.

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?

Output schema exists, so return values are covered. Description lacks details on error handling, whether appending or replacing, and default list creation. Adequate but could add more operational 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?

Schema description coverage is 0%, so description must compensate. It explains list_name's purpose (omit for primary list) but does not clarify recipe_ids beyond being IDs. Adds some meaning but incomplete.

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 adds ingredients from multiple recipes to a shopping list, with merging of same items. This distinguishes it from siblings like add_recipe_to_shopping_list (singular) and add_items (generic).

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 advises to omit list_name for the primary list, giving clear context on when to use the parameter. However, it does not explicitly state when not to use this tool compared to alternatives, though the name and sibling list imply it's for multiple recipes.

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