add_shopping_list_items

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

With no annotations, the description carries the behavioral burden. It discloses that the tool adds items, guesses aisles, and reuses stores, and states it returns the created lines. It does not mention permissions or side effects beyond adding, but the core behavior is well covered.

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?

Two sentences with no filler. The purpose is front-loaded, and the optional-field behavior is explained in a compact, logical sequence. Every sentence adds value.

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 is complete for an add operation: it covers the required fields, the optional behavior, and the return value. It does not address error handling or prerequisites, but for this simple tool, nothing critical is missing.

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 coverage is 0% per context, so the description must compensate. It explains the semantics of category_id and store_id beyond their schema descriptions, and clarifies that title is required. It does not explain note, unit, or amount, but those are straightforward and their schema descriptions suffice.

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 verb 'Add' and the resource 'shopping list', and explains behavior around optional fields. It is unambiguous and distinct from sibling tools like update_shopping_list_items or remove_shopping_list_items, even without naming them.

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?

It gives clear usage guidance: only title is required, and explains what happens when category_id or store_id are omitted. It implies this is the tool for adding new items, though it does not explicitly contrast with alternatives. The fallback behavior is a strong usage cue.

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