add_items

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention whether items are appended or overwritten, if duplicates are allowed, if the list must exist, or any constraints like maximum items. This is a significant gap for a mutation tool.

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 sentences, front-loaded with the main action and key usage tip. No filler words; every sentence is necessary and direct.

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 tool's simplicity and the presence of an output schema (handling return values), the description covers basic usage. However, it lacks details on behavioral aspects (e.g., error handling, list existence) and edge cases, making it only minimally complete for an agent.

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 compensates by explaining 'items' as free text with examples and noting that 'list_name' defaults to the primary list when omitted. This adds practical value, though it could specify format or limits.

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 adds one or more free-text items to a shopping list, specifying examples like 'milk' and '2 kg potatoes'. It differentiates from siblings such as 'add_product_to_shopping_list' and 'add_recipes_to_shopping_list', which handle structured or specific types.

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 guidance to omit 'list_name' for the primary list, indicating default behavior. While it does not explicitly exclude alternatives, the sibling tool names imply distinct use cases (e.g., adding products vs. free text), making the context clear.

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