Update an existing household shopping list by ID with new list items, names, or metadata. Keep shopping lists accurate and current for your household.
Update One [PUT /api/households/shopping/lists/{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 are provided, and the description discloses no behavioral traits. It does not mention that this is a mutation, required permissions, or side effects. The agent has no insight beyond 'update'.
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 under-specified. The single line does not earn its place because it conveys minimal useful information. It is missing critical details, making it an underspecification rather than proper conciseness.
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 complex input schema with nested objects and no annotations or output schema, the description is completely inadequate. It fails to provide the context needed for an agent to use the tool correctly.
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 coverage is 0%, and the description adds no meaning to the parameters. item_id and the body are completely unexplained. The agent cannot distinguish what values to provide.
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 'Update One' is essentially a tautology of the tool name. It does not specify what resource is updated (shopping list), what fields, or the effect. Slightly better than missing, but still vague.
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 siblings like households_shopping_list_items_update_one or households_shopping_lists_create_one. The agent cannot infer the correct context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.