Turn a list of foods into a reusable meal template with serving sizes and macro details, so you can log common meals without re-entering nutrition data.
Create a reusable meal template from a list of foods
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Template name (e.g., "Morning Oatmeal", "Post-Workout Shake") | |
| items | Yes | Food items in the template |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral disclosure burden. It only states that a template is created, with no mention of return values, duplicate handling, validation behavior, or side effects.
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?
One sentence, no filler, with the action and resource front-loaded. Every word contributes to understanding the tool's purpose.
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 schema covers the inputs well, but with no annotations and no output schema, the description omits practical behavior details such as what happens after creation or how the template can be used subsequently. It is minimally viable but leaves room for confusion.
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 description coverage is 100%, so the schema already documents both 'name' and 'items' thoroughly with examples and per-field units. The description adds no new parameter detail, which matches the baseline for full schema coverage.
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 states a clear verb ('Create'), a specific resource ('reusable meal template'), and the input source ('from a list of foods'). This cleanly distinguishes it from siblings like update_meal_template, delete_meal_template, and create_meal_entry.
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 phrase 'reusable meal template' implies this is for saving a template rather than logging a one-time meal entry, giving some contextual guidance. However, it does not explicitly name alternatives or state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.