create_households_cookbooksCreate a household cookbook in Mealie by providing details such as name, slug, public status, position, description, language, and query filter to organize recipes for the household.
Create One
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| slug | No | ||
| public | No | ||
| position | No | ||
| description | No | ||
| accept-language | No | ||
| queryFilterString | 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 full burden of behavioral disclosure, but 'Create One' reveals nothing about side effects, required permissions, idempotency, validation rules, or consequences of invoking the tool. The agent only knows that something is being created, which is already evident from the tool name.
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?
The description is short but under-specified rather than concise; two words cannot carry the necessary semantic weight. There is no structure, no front-loaded key information, and every word simply restates the tool name.
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?
Even with an output schema present, the description is nowhere near complete for a tool with 7 parameters, no schema descriptions, and no annotations. An agent cannot determine correct invocation, parameter semantics, or relationship to households, making this definition inadequate for reliable selection and use.
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?
The input schema has 7 parameters and 0% schema description coverage, so the description must compensate by explaining what fields like 'slug', 'public', 'position', and 'queryFilterString' mean, but it does not mention any of them. The description contributes no parameter-level meaning at all.
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 'Create One' is a tautology that merely restates the verb 'create' from the tool name and title without specifying the resource or adding any distinguishing meaning. The agent must rely entirely on the name 'create_households_cookbooks' to infer what is being created, and even then the description offers no clarity about what a cookbook entails.
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 description provides no guidance on when to use this tool versus the many sibling create_households_* tools. It does not state situations where this tool is appropriate, nor does it mention any alternatives or exclusions, leaving the agent without decision-relevant context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.