add_item

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

With no annotations, the description carries full burden. It discloses that the tool returns the created item and list stats, including remaining capacity for free lists—a useful behavioral detail. However, it does not mention idempotency, error conditions, or side effects (e.g., does it fail if list is full?). No contradictions with annotations (none 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 consists of two tight sentences with no wasted words. The first sentence front-loads the core purpose, and the second sentence adds valuable return information. 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?

Given the tool's simplicity and the lack of an output schema, the description adequately explains the return value (item + stats + capacity info). However, it omits error conditions, authentication requirements, and prerequisites (e.g., list must exist). The mention of 'free lists' hints at a capacity limit, but the behavior when full is not described. Sibling 'upgrade_list' suggests a related concept, but cross-reference 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 description coverage is 100%, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema already provides (e.g., 'list_id' is just 'The list ID'). No value is added by the description for parameter understanding.

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 uses a specific verb ('Add') and resource ('item to a punch list'), clearly stating the action. It distinguishes from sibling tools like 'create_list' (which creates lists) and 'list_items' (which lists items), leaving no ambiguity about the tool's function.

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 implies the tool is for adding items, but does not explicitly state when to use it versus alternatives like 'update_item' or 'flag_item'. No exclusions or context about prerequisites (e.g., list must exist) are provided, leaving usage guidance implicit.

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