households_recipe_actions_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 burden. It never states that the operation is read-only (only the buried 'read-only' keyword hints at it), nor does it describe pagination behavior for what is clearly a paginated list endpoint, nor any auth or filtering semantics.

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 first two sentences are efficient and front-loaded, but the enormous keyword block (nearly every synonym of 'list recipe actions' plus 'mealie') is pure filler that bloats the definition without adding meaning. Keyword stuffing should be replaced by real behavioral and parameter detail.

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 7-parameter paginated list tool with no annotations and no output schema, the agent needs to know filtering/pagination semantics and the shape of the returned list. None of that is present; the only content beyond the name is a keyword dump.

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 provides no explanation of any of the 7 parameters (page, orderBy, perPage, queryFilter, orderDirection, paginationSeed, orderByNullPosition). With undocumented, non-obvious params like paginationSeed and orderByNullPosition, the description fails to compensate 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 opening line 'Get All — Households: Recipe Actions. List recipe actions.' states a clear verb (list/get) and resource (household recipe actions), and the URL path confirms the endpoint. However, it does nothing to distinguish this from the sibling households_recipe_actions_get_one, so an agent cannot tell the collection vs single-resource tools apart from the text alone.

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 versus households_recipe_actions_get_one, create_one, or the other recipe-action siblings. The trailing keyword list is a retrieval hack, not usage guidance, and no prerequisites or context are given.

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