add_recipe_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 only states the action and scale multiplication. Lacks disclosure of side effects (e.g., overwriting existing items), authorization needs, or error behavior. For a mutation tool, this is insufficient.

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?

Description is very concise with two sentences. No filler words. However, adding more structured information (e.g., formatting, prerequisites) would improve without bloating.

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?

Tool has 3 required parameters, no output schema, no annotations, and many siblings. Description is too minimal. It does not explain return value, prerequisites (e.g., list existence), behavior if recipe not found, or how scale interacts with ingredient amounts. Incomplete for a production tool.

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 'scale' as multiplying amounts, which adds some meaning. But list_id and recipe_id are left unexplained. Description adds minimal value beyond the schema.

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?

Description clearly states verb 'add' and resource 'recipe's ingredients to a shopping list'. It specifies the core action and distinguishes from siblings like create_shopping_item (adds individual items) and remove_recipe_from_shopping_list (removes).

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?

No explicit guidance on when to use this tool vs alternatives. With many sibling tools for creating items or lists, the description should mention prerequisites (e.g., list must exist) or when not to use it. Only a brief note on the scale parameter.

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