add_recipe_ingredients_to_list

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say the operation mutates a shopping list, what happens to existing items, whether it is idempotent, or what permissions are needed. The misleading 'Create recipe' phrase actively adds confusion rather than 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?

The purpose is front-loaded, but roughly half the text is a ~50-term keyword dump ('recipe, households, shopping, lists, create, add, new, make, write, post, mealie') that consumes space without adding meaning. Wasteful rather than concise.

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?

No annotations, no output schema, and 0% parameter description coverage for a mutating endpoint that takes a complex nested bulk body. An agent cannot determine authentication needs, response shape, or how to construct the body from this definition alone; it covers the endpoint and rough purpose but little else.

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% and the body is a deeply nested array of ShoppingListAddRecipeParamsBulk objects (recipeId, recipeIngredients, recipeIncrementQuantity) with no field descriptions anywhere. The description compensates only implicitly through its title, giving no semantics for item_id, recipeId, or the increment quantity.

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 title phrase 'Add Recipe Ingredients To List' names a specific verb and resource, so the core purpose is identifiable. However, the immediately following 'Create recipe' contradicts that framing (this endpoint attaches recipe ingredients to an existing shopping list, it does not create a recipe), and there is no differentiation from the sibling 'add_single_recipe_ingredients_to_list' or 'remove_recipe_ingredients_from_list'.

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?

There is no guidance on when to use this bulk endpoint versus 'add_single_recipe_ingredients_to_list', nor any prerequisite or context statement. The remainder of the text is a keyword dump, not usage instruction.

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