mealie_get_todays_meals

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

With no annotations, the description carries the full burden. 'Fetch' clearly indicates a read-only operation, and 'today's household meal plan entries' adds scoping. However, it does not explicitly mention the absence of side effects, return format, or any potential edge cases (e.g., empty results), so it provides only basic behavioral clarity.

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 concise sentence, front-loaded with the action ('Fetch') and the resource. It wastes no words and is immediately scannable for an agent.

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 zero-parameter read-only tool, the description is sufficiently complete. It names the resource and timeframe, and given the absence of an output schema, the description provides enough context for an agent to know what the tool returns conceptually. It could be slightly richer to mention the distinction from list_mealplans, but overall it is adequate.

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 tool has zero parameters, so the schema is trivially complete. The description correctly avoids inventing parameters, and there is nothing meaningful to add beyond the schema. Baseline for 0 params is 4, and the description does not undermine this.

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 the specific verb 'Fetch' and clearly identifies the resource (today's household meal plan entries), distinguishing it from siblings like mealie_list_mealplans (which presumably covers all dates) and the create/update/delete mealplan tools. The scope is explicit with 'today's household'.

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 word 'today's' implies the intended use case, but the description does not explicitly state when to use this tool over alternatives like mealie_list_mealplans. There is no mention of exclusions or alternative tools for other date ranges, making the usage guidance only implicitly understood.

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