mealie_list_mealplans

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 only mentions date format, but fails to disclose pagination behavior (page, per_page), default date ranges, or return value shape. This leaves significant unknowns about how the tool behaves when invoked.

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 only two short sentences and wastes no words. It leads with the core purpose ('List household meal plans') and adds a relevant note about date format, making it efficiently front-loaded.

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?

Although an output schema exists (reducing the need to describe return values), the description omits essential context about pagination and date filtering semantics. With 4 optional parameters and no annotations, this under-specification makes it difficult for the agent to select and calibrate the call correctly.

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 for the 4 parameters. It adds meaning only to start_date and end_date by specifying 'ISO yyyy-mm-dd strings,' but says nothing about page or per_page, their defaults, or their interaction. This minimal compensation is inadequate for the schema gap.

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 'List' and identifies the resource 'household meal plans,' clearly indicating the tool enumerates meal plans. This distinguishes it from siblings like mealie_get_todays_meals (which retrieves a specific day's meals) and create/update/delete actions.

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 usage context is implied by the name and basic purpose, but the description does not explicitly state when to use this tool versus alternatives like mealie_get_todays_meals or mealie_list_shopping_lists. No exclusions or alternative tool references are provided, leaving the agent to infer applicability.

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