create_admin_householdsCreate an admin household in Mealie to manage household settings and gain administrative control over recipes, meal plans, and shopping lists.
Create One
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| groupId | No | ||
| 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 provided, the description must disclose behavior, but 'Create One' only implies a vague creation action. It says nothing about side effects, permissions, required relationships, idempotency, or response behavior.
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 extremely short, but this is under-specification rather than effective conciseness. 'Create One' does not earn its place because it provides no actionable information.
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?
Although an output schema exists, the description is far too incomplete to guide correct invocation. An agent has no idea what a valid request looks like, what the tool does, or how it differs from dozens of sibling 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%, so the description must compensate, but it adds no meaning to any of the three parameters. It does not clarify what 'name', 'groupId', or 'accept-language' represent or how they relate to creating an admin household.
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' contains only a verb and a nonspecific pronoun. It fails to identify the resource being created (admin households), so an agent cannot tell what this tool does or distinguish it from sibling create tools like create_admin_users or create_admin_groups.
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?
There is no guidance on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions, and the large sibling list provides no clarifying contrast.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.