List meal plan entries

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

Annotations declare readOnlyHint true, so the description doesn't need to reiterate read-only nature. However, it adds value by disclosing that entries are either recipe references or notes, which is beyond schema. It does not describe pagination, ordering, or behavior with empty results. No contradictions with annotations.

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, completely front-loaded with the purpose and a detail about entry types. Every word earns its place with no fluff or repetition.

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?

Given 4 optional params and no output schema, the description provides essential meaning but leaves gaps. It does not explain default behavior when start/end date are omitted (e.g., full plan or recent range?), nor the order of entries or pagination behavior. The mention of entry types is helpful, but more context about return format or behavioral defaults 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 coverage is 100% with each parameter already having a description (page, end_date, per_page, start_date). The tool description does not add any additional meaning or constraints beyond what the schema provides. Baseline 3 is appropriate.

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 lists meal plan entries for a household within a date range. It specifies the verb 'Lists' and the resource 'meal plan of the household', and distinguishes the output as either recipe references or free-text notes. This clearly differentiates it from sibling tools like get_todays_meals (likely single day) and create/update/delete meal plan entries.

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 is for viewing meal plans over a date range, but it does not explicitly state when to use this versus alternatives like get_todays_meals or create_mealplan_entry. No guidance on when not to use, prerequisites, or exclusions is provided.

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