update_households_cookbooksUpdate multiple household cookbooks in one request by providing an array of cookbook objects with their IDs and fields to modify.
Update Many
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| accept-language | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. 'Update Many' only reveals that this is a bulk mutation; it does not state whether updates replace whole records, whether partial fields are allowed, what errors may occur, or how the response is shaped.
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?
Two words are concise, but this is under-specification rather than effective concision. Valuable context about the batch payload and endpoint behavior is absent.
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 input schema is a complex array of objects, the sibling list is large, and there are no annotations to compensate. The description omits what the operation updates, what constraints apply, and how to construct a valid request, making it inadequate for correct invocation.
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% and the description adds no parameter information. The body array requires objects with id, name, groupId, householdId and additional optional fields, but the description neither lists them nor explains semantics.
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?
Combined with the title 'Update Households Cookbooks', the description 'Update Many' states the verb (update) and the resource (households cookbooks), and the word 'Many' signals batch scope. This distinguishes it from the single-item sibling update_households_cookbooks_by_item, though the description itself omits the resource.
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 over alternatives. The word 'Many' implies bulk use, but there are no conditions, exclusions, or references to list_households_cookbooks or update_households_cookbooks_by_item.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.