Get today's meals

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

With readOnlyHint=true already indicating a safe read operation, the description adds valuable behavioral detail: the response is a bare list rather than a paginated envelope, and the date calculation follows Mealie's household 'today' logic. This goes beyond the annotation's safety hint and informs the agent of response shape and timezone nuances.

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 succinct at two sentences, front-loaded with the primary action, and every clause adds value: the return content, the household-specific date handling, and the response format. There is zero filler.

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 parameterless read-only tool with no output schema, the description is complete: it states what is returned, how the date is determined, and the response shape. No additional context is needed for an agent to select and invoke this tool 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?

The tool has zero parameters, so there is no parameter semantics to describe. The schema coverage is trivially 100% with an empty properties object. The description compensates by clarifying the tool's purpose, which is sufficient for a no-argument tool.

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 tool returns recipes planned for today, with the specific verb 'Returns' and resource 'recipes planned for today.' It distinguishes from sibling tools like list_mealplans by focusing on today's meals specifically, and adds the nuance of how Mealie computes 'today' for the 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 description implies when to use this tool (when you need today's meals) and provides context about the response format, but it does not explicitly mention alternatives or exclusions. However, the sibling list includes list_mealplans, which could be an alternative for broader queries, and the description makes the tool's specific scope clear enough.

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