households_mealplans_get_all

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

No annotations are provided, so the description carries the full behavioral burden, yet it only restates the endpoint. It says nothing about pagination, default ordering (orderDirection=desc), date-range filtering, or what the response contains.

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 two core sentences are appropriately front-loaded and useful, but they are buried under a large keyword spam list (dozens of near-synonyms and single words like 'read', 'mealie') that adds no selection value and inflates the size substantially.

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 9-parameter list endpoint with no annotations and no output schema, the description omits everything an agent needs beyond the resource name: pagination behavior, sort options, date filtering, and return shape. It is not adequate to call 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?

Nine parameters exist with 0% schema description coverage, including non-obvious ones like page, perPage, orderBy, orderDirection, orderByNullPosition, start_date/end_date, queryFilter, and paginationSeed. The description explains none of them, so an agent gets no help on how to filter, sort, or paginate meal plans.

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 states a clear verb+resource — 'List meal plans' — and the endpoint [GET /api/households/mealplans] confirms it is a read of household meal plans. The 'Get All' prefix distinguishes it from the sibling households_mealplans_get_one, though it does not otherwise differentiate from get_todays_meals or households_mealplan_rules_get_all.

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 mention of alternatives, and no exclusions. The only implicit signal is the 'Get All' naming versus get_one, which the agent must infer rather than being told.

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