Suggest next meal

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

The description is consistent with annotations (readOnlyHint, idempotentHint, destructiveHint) but adds little behavioral detail beyond stating it suggests a meal. It does not explain what happens if no intake is logged or how wearable context integrates, but the annotations already cover safety aspects.

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 sentence, which is concise but too brief for a tool with 9 parameters. It is front-loaded with the verb but lacks structure or additional details that would improve clarity.

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 fails to explain what the suggestion output looks like and does not compensate for the missing output schema. Given the tool's complexity (9 parameters, nested objects), the description is insufficient for an agent to fully understand its behavior.

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?

With only 11% schema coverage, the description minimally explains parameters. It mentions 'optional wearable context' but does not describe the meaning of focus, locale, meal_type, or other parameters. The auto_wearable parameter has a description in the schema, but the tool description adds no further clarity.

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 suggests a next meal based on specific data sources (intake, goals, memory, wearable context). However, it does not differentiate from sibling tools like nourish_estimate_meal or nourish_pre_workout_nutrition, which could also provide meal suggestions.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, such as if no intake data is available, nor does it reference other sibling tools.

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