mealie_add_shopping_item

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral requirement of user confirmation, which is valuable. However, it does not mention side effects, the need for the shopping list to exist, or the nature of the response beyond what the output schema might indicate.

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 a single, well-structured sentence that is front-loaded with the core action and adds a necessary context clue. No wasted words.

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?

For a tool with six parameters and no annotations, the description is overly terse. It does not clarify what 'display' refers to, how to specify the shopping list, or the meaning of 'quantity', 'note', and 'checked'. The existence of an output schema mitigates return-value concerns, but the input side remains under-specified.

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 schema has 0% description coverage, leaving all parameter explanation to the description. The description only indirectly hints at the 'confirmed_by_user' parameter via 'explicit user confirmation' but says nothing about 'shopping_list_id', 'display', 'quantity', 'note', or 'checked'. This is insufficient for a tool with six parameters.

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 function: 'Add an item to a shopping list' with a specific verb and resource. It also includes a qualifier 'after explicit user confirmation,' which distinguishes this from similar shopping-list tools like update or delete.

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 phrase 'after explicit user confirmation' provides clear guidance on when the tool should be invoked—only after user confirmation. It does not explicitly name alternatives, but the context is sufficient for an agent to know not to use it without confirmation.

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