add_recipe_to_shopping_list

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

No annotations provided, so the description carries full burden. It accurately conveys the additive behavior without hinting at destructive actions. It could be more explicit about error conditions (e.g., non-existent recipe or list), but the core behavior is clear.

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 extremely concise: two sentences, front-loaded with the main action, followed by a succinct usage tip. No wasted words.

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 primary purpose and key parameter guidance. With an output schema present, return values are documented elsewhere. Missing details like error handling or behavior when list_name is omitted (besides primary list) are minor gaps.

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?

With 0% schema description coverage, the description should explain both parameters. It only mentions list_name (omit for primary) but does not explain recipe_id or the meaning of list_name (name of the shopping list). The example '8 dl mjölk' refers to ingredient format, not parameter syntax.

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 'Add all ingredients from a recipe as items to a shopping list' with a concrete example. It distinguishes this tool from siblings like add_product_to_shopping_list (single product) and add_items (arbitrary items).

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, providing clear context for when to exclude the parameter. However, it does not explicitly compare to sibling tools or state when this tool should be preferred.

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