keep_add_items

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully reveals that items are added unchecked and that duplicates are not prevented automatically. However, it does not explain side effects such as how the target list is resolved via note_id or list_title, or what happens if the target does not exist.

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 tight sentences. The purpose is front-loaded, and the second sentence adds a valuable caveat without redundancy. Every sentence earns its place.

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 main workflow and the duplicate-prevention concern, which is essential. But it leaves the distinction between note_id and list_title unexplained, and does not clarify whether the shopping list is the default target. This makes the description minimally viable but incomplete for confident use with optional parameters.

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%, and the description only hints at 'items' through 'one or more ... items'. The optional parameters note_id and list_title, which determine which checklist is modified, are not explained at all, leaving a meaningful gap for correct invocation.

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 names a specific verb ('Add'), a concrete resource ('one or more unchecked items to a Keep checklist (the shopping list)'), and the resulting item state ('unchecked'). This clearly distinguishes the tool from siblings like keep_check_items, keep_uncheck_items, and keep_remove_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?

It gives actionable usage guidance: 'check keep_get first' to avoid duplicates, and it frames the target as the shopping list. It does not explicitly state when not to use this tool versus siblings like keep_check_items or keep_remove_items, so it falls short of a 5.

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