mealie_create_shopping_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the need for user confirmation but does not explain what happens if confirmed_by_user is false, whether the operation is destructive or reversible, or any side effects. This is minimal transparency 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 a single, efficient sentence that front-loads the core action. Every word earns its place, and there is no redundant information.

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?

Despite having an output schema (so return values need no explanation), the description is incomplete for a tool with two parameters and zero schema descriptions. It lacks necessary details about parameter usage, the confirmation requirement, and how this creation tool fits with sibling operations, leaving significant gaps for an agent to safely invoke it.

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%, so the description must compensate. It only hints at the confirmed_by_user parameter through 'explicit user confirmation', but it does not explain the name parameter or the semantics of the boolean flag (e.g., must be true, default false). It adds little beyond the schema.

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 ('Create') and resource ('shopping list'), clearly indicating the tool's action. It also distinguishes itself from siblings like mealie_add_shopping_item and mealie_get_shopping_list by focusing on creation, and the nuance 'after explicit user confirmation' adds a unique behavioral scope.

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 that this tool should be used only after explicit user confirmation, which is a clear contextual signal. However, it does not explicitly mention when not to use it or compare it to alternatives such as adding items to an existing list, leaving the guidance somewhat implicit.

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