mealie_get_shopping_list

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states that it fetches a shopping list by id, but does not disclose whether the response includes items, how errors are handled (e.g., 404 if not found), or any permission requirements. Reads more like a tautological statement of the tool's function.

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, front-loaded sentence with no unnecessary words or repetition. It communicates the essential action, target, and method efficiently.

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 simple single-parameter fetch tool with an output schema, the description is adequate but leaves some ambiguity about the scope of the returned object (e.g., full list with items versus metadata only). It does not reference sibling tools like list_shopping_lists to set expectations, and it lacks any detail about when to use this tool in a broader workflow.

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, and the description does not elaborate on the shopping_list_id parameter beyond confirming it is the identifier used to fetch the list. The parameter name and title make it somewhat self-explanatory, but the description adds no format, type details, or examples, so it does not fully compensate for the schema's lack of documentation.

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 'Fetch' with a specific resource 'household shopping list' and identifies the lookup method 'by id'. This clearly differentiates it from sibling tools like mealie_list_shopping_lists (which fetches multiple) and mealie_get_shopping_item (which fetches an 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 implies the tool should be used when you have a specific shopping_list_id, but it does not explicitly state when to use it versus alternatives like mealie_list_shopping_lists or mealie_get_shopping_item. There is no 'when not to use' guidance.

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