bar_add_to_shopping_list

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

No annotations are provided, so the description carries the full burden. It says 'add' which implies mutation, but doesn't state whether additions are idempotent, whether user_id defaults to a specific user, whether duplicates are allowed, or what the response confirms.

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?

A single short sentence is technically concise but is under-specified rather than efficient. It leaves out required context instead of front-loading useful information.

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?

A mutation tool with no annotations, no output-schema explanation needed (output schema exists), and zero schema parameter coverage. The description does not provide enough for an agent to invoke it correctly, especially regarding the user_id default and array handling.

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 the description must compensate for two undocumented parameters. It says 'ingredients' which loosely maps to ingredient_ids, but adds nothing about the user_id default, array semantics, or valid ID ranges.

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?

States a clear verb+resource: 'Add ingredients to the shopping list.' An agent can tell what it does. However, it doesn't distinguish this from the sibling bar_get_shopping_list or explain scope relative to it, so it's vague on differentiation.

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 guidance on when to use this vs. bar_get_shopping_list or bar_add_to_shelf. An agent has to infer that this mutates a shopping list while the sibling only reads it. No prerequisites or context given.

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