Update an existing household meal plan rule by its ID. Modify the scheduled day, meal type, or query filter to keep your meal planning accurate.
Update One [PUT /api/households/mealplans/rules/{item_id}]
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| item_id | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description does not disclose behavioral traits such as side effects, authorization requirements, rate limits, or what fields are modified. For a mutation tool, this is critically incomplete.
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?
Extremely concise (two lines), but so minimal that it becomes unhelpful. The endpoint is included but adds little structure or 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?
Given the complexity of an update tool with nested input and no output schema, the description is completely inadequate. It does not explain what a mealplan rule is, which fields are updatable, or what the response looks like.
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 has two parameters (item_id and body) with 0% description coverage. The description does not explain what item_id represents or what the nested PlanRulesCreate object contains (day, entryType, queryFilterString). The description adds no semantic value beyond the schema.
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 only says 'Update One' and includes the HTTP endpoint. This barely adds beyond the tool name, which already indicates it updates a specific resource. No indication of what is updated or how it differs from create/delete/get siblings.
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?
No guidance on when to use this tool versus alternatives like create, delete, or get. The agent receives no context about prerequisites, typical use cases, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.