mealie_list_shopping_items

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

With no annotations provided, the description carries the burden of disclosing behavior. It implies a read-only 'List' operation and mentions filter options, but it doesn't disclose pagination behavior (page/per_page) or potential output size limits. For a simple listing tool, this is adequate but not rich.

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?

A single, well-structured sentence delivers all the core information: what it lists and the optional filters. No wasted words, ideal conciseness.

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?

The tool is relatively simple, has an output schema, and no nested objects. However, given no annotations and missing pagination description, the tool is adequate but incomplete for an agent that might need to handle large result sets. More detail on pagination or result set behavior would improve completeness.

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 explains 'shopping list' and 'checked' filters, but completely omits 'page' and 'per_page', which are important for pagination. Thus it only partially explains the 4 parameters, leaving half undocumented in both schema and description.

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 verb 'List' and the resource 'shopping list items', with optional filters by shopping list and checked state. This distinguishes it from sibling tools like 'mealie_get_shopping_list' (which retrieves a whole list) and 'mealie_get_shopping_item' (singular item), making the purpose unambiguous.

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 gives clear context for when to use this tool—when listing shopping list items—and mentions optional filtering capabilities. It doesn't explicitly name alternatives or exclusionary conditions, but the usage context is clear enough for an agent to select it appropriately among siblings.

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