add_list_items

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

With no annotations, the description carries full burden for behavioral disclosure. It only states basic action and constraints (unique names, parent/subsets). Missing critical behavioral traits: what happens on duplicate names, error handling, rate limits, or whether the operation is atomic. This is insufficient 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 only three sentences, all front-loaded with purpose, features, and actionable guidance. No unnecessary words; every sentence provides 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?

Given the complexity (4 required params, no output schema, no annotations), the description covers basic purpose and constraints but lacks return value information and error conditions. It is minimally viable but leaves gaps for an agent to understand what happens after invocation.

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 100%, so baseline is 3. The description adds value by emphasizing 'parent (hierarchy placement)' and 'subsets (subset membership)', and introducing the constraint 'Item names must be unique' which is not in the schema. This extra context justifies a higher score.

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 'Add new items to a list', providing a specific verb and resource. It distinguishes from sibling tools like update_list_items by focusing on 'new' items. The mention of parent and subsets adds specificity.

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 gives clear context with 'Use show_lists to find listId' and the constraint 'Item names must be unique'. However, it does not explicitly state when not to use this tool (e.g., for modifications, use update_list_items), missing exclusion guidance.

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