list_households_cookbooks

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

No annotations are provided, so the description must disclose behavioral traits like pagination, idempotency, or side effects. It does not even state that this is a read operation or that it returns a list, leaving the agent completely in the dark.

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?

While only two words, the description lacks substance—it is under-specified rather than concise. Every sentence should earn its place, but here 'Get All' fails to convey essential information about the tool's function.

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?

Given the presence of an output schema and 8 parameters, the description is completely inadequate. It does not explain what the tool returns, how to interpret the output, or any constraints (e.g., pagination limits).

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 adds no meaning to any of the 8 parameters (e.g., page, orderBy, queryFilter). The description 'Get All' is too vague to help an agent understand how to use these parameters effectively.

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 'Get All' is a tautology that provides no specific verb or resource. It does not clarify that the tool lists all cookbooks for a household, nor does it differentiate from sibling tools like 'list_households_mealplans' or 'get_households_cookbooks_by_item'.

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. With many sibling list and get tools, the description should indicate that this is for retrieving all cookbooks (likely paginated) as opposed to a single item or other entity types.

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