add_recipe_to_shopping_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('add all ingredients') without explaining side effects such as whether ingredients are merged with existing list items, whether the list is cleared first, or what the response contains. It also does not mention permissions or idempotency.

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 short sentences with no filler. The main purpose is front-loaded, and the optional quantity note is succinctly added. Every word contributes meaning.

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?

Given the absence of annotations and output schema, the description is incomplete for a mutation tool. It does not clarify whether the operation appends or replaces existing shopping list items, how quantities are scaled, or what the function returns. While the schema covers parameters, the behavioral context is lacking.

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 100%, so the baseline is 3. The description's mention of 'Optionally specify quantity for multiple servings' adds a small semantic hint about recipeQuantity, but the schema already describes it as 'Number of servings/portions to add (default: 1)'. The description does not significantly exceed schema information.

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's function: 'Add all ingredients from a recipe to a shopping list.' It uses a specific verb ('add') and identifies both the source (recipe) and destination (shopping list). The phrase 'all ingredients' implicitly distinguishes it from sibling tools like add_shopping_list_item, which add a single item.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or contrast with related tools such as add_shopping_list_item or create_recipe. The optional quantity note implies scaling use cases but does not constitute clear usage direction.

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