seed_units

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden, yet it only states the HTTP method and path. It does not say what defaults are seeded, whether the operation is idempotent, what auth/permissions are required, or what happens to existing units.

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 actionable sentence is buried under a redundant title echo and a long SEO keyword list ("seed_units, seed units, create unit, add unit... post, mealie"). The keyword padding crowds out real guidance rather than adding it.

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?

For a mutation tool with no annotations, no output schema, an undocumented nested body, and an ambiguous seed-vs-create identity, the description supplies none of the missing behavioral or parameter context an agent needs to call it 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 description coverage is 0% for the single required `body` parameter, whose only documented field is `locale`. The description says nothing about the body, locale, or any accepted values, so it fails to compensate for the coverage gap.

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 does contain a verb+resource ("Create unit") and an endpoint (POST /api/groups/seeders/units), so the basic action is identifiable. However, the name/title "Seed Units" reads as a bulk-seeding operation while the body says "Create unit," and it never distinguishes itself from the sibling recipes_units_create_one. The ambiguity leaves an agent guessing what is actually created.

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 when-to-use guidance, no prerequisites, and no routing to alternatives such as recipes_units_create_one or seed_foods/seed_labels. The agent gets no basis for choosing this tool over a sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.