Update a household's recipe action by ID, changing its URL, title, action type, group, or household. Modify or correct existing recipe links or posts with this endpoint.
Update One [PUT /api/households/recipe-actions/{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 exist, so the description must carry the full burden. It discloses no behavioral traits such as destructive potential, authentication needs, or side effects. The description is essentially the endpoint URL.
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 short but at the expense of all useful information. This is not conciseness but under-specification. The description fails to earn its place by providing any value.
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 tool's complexity (nested schema, multiple sibling CRUD tools), the description is completely inadequate. It provides no context about the domain (recipe actions), required fields, or how it relates to other tools.
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 0%, meaning the schema provides no parameter descriptions. The description adds no meaning to the parameters (e.g., what actionType values mean, how groupId and householdId are used). It is purely the endpoint.
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?
Description just restates the tool name ('Update One') and the HTTP endpoint, adding no information beyond what the name already implies. It does not explain what a recipe action is or what the tool does in a meaningful way.
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 provided on when to use this tool versus siblings like create, delete, or get. The description lacks context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.