households_cookbooks_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. It implies a read-only list via the endpoint but says nothing about household scoping, permissions, defaults, result shape, or pagination behavior for a 7-parameter paginated endpoint.

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 sentence is crisp and front-loaded, but it is followed by an enormous keyword list that adds no decision value and bloats the definition. The useful content and the filler are roughly equal in size, which dilutes the message.

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 paginated list tool with no output schema and no annotations, the description should at least explain pagination/filtering basics and how results are scoped to the household. None of that is present, so it is incomplete for correct invocation.

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% across 7 parameters (page, perPage, orderBy, orderDirection, queryFilter, paginationSeed, orderByNullPosition). The description adds no meaning for any of them, leaving pagination and filtering semantics entirely unexplained.

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?

States a specific verb and resource: 'List cookbooks', with the backing endpoint [GET /api/households/cookbooks]. However, it does not differentiate from close siblings like households_cookbooks_get_one or explore_cookbooks_get_all, so an agent can't tell which 'list' tool applies to household-scoped cookbooks without inspecting schemas.

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 the sibling get_one, or versus explore_cookbooks_get_all. The long 'Keywords:' block is a recall-oriented synonym dump, not usage context, so the agent gets no when/when-not signal.

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