list_meals

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

Annotations already declare it read-only and idempotent, lowering the bar. The description adds useful behavioral context beyond the annotations, such as timezone resolution for dates, the 31-day maximum range, and the recommendation to make multiple calls for longer periods. This enhances transparency without contradicting the 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 long but well-structured, with clear sections for usage, ranges, and inference rules. While it repeats some schema information, the added guidance on when to call and how to handle date ranges is valuable and not redundant. The organization makes it easy to parse.

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 description covers when to use the tool, what it returns (meals with fields), limitations (max range, multi-call strategy), and parameter handling. Given that an output schema exists, an agent has all necessary information to decide when and how to call this tool successfully.

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 schema covers 100% of parameters with detailed descriptions (format, optionality, meaning), establishing a baseline of 3. The main description adds extra semantic context, particularly the inference rules for date and end_date (e.g., "this week" maps to Monday through today), which helps agents interpret parameter values correctly.

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's function: 'List all meals logged for a date or date range, including each meal's ID, date, type, food description, and macros.' It also distinguishes itself from sibling tools by noting that update_meal and delete_meal can resolve meals without this tool, making the purpose and scope 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?

Explicit usage scenarios are provided: 'use it to answer "what did I eat today/this week/yesterday?", review what has been logged, or get an id after an ambiguous update_meal/delete_meal match.' It also gives practical guidance on date ranges and multi-call handling, and clarifies that it is not required before update/delete operations.

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