add_item

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 the action ('Add') and parameter roles. It does not reveal whether adding an item is idempotent, whether duplicate names are handled, or any side effects (e.g., if the list must exist). This is insufficient for safe tool invocation.

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 concise (three lines for params, one line for purpose) and well-structured with an explicit Args section. Every sentence adds value without redundancy.

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 no output schema, no annotations, and 3 params, the description is adequate but incomplete. It lacks information about return values, error conditions, or required state (e.g., list must exist). For a simple tool, minimum viable but could be improved with a note on behavior.

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?

The input schema has 0% description coverage, but the description adds semantic clarity: it explains list_id as 'numeric ID', name as 'Name of the item', and amount as 'Optional amount or quantity'. This helps the agent understand parameter meaning beyond type and default.

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's purpose: 'Add an item to a shopping list.' It uses a specific verb ('Add') and resource ('item to a shopping list'), and it is distinct from sibling tools like create_list (creates list) and delete_item (deletes item).

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, constraints, or cases where other tools (e.g., update_item_amount) might be more appropriate. The user must infer usage from the tool name alone.

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