list_households_mealplans

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description 'Get All' reveals nothing about pagination, authentication, rate limits, or what the tool returns (e.g., a list). It does not contradict annotations because none exist, but it provides no behavioral context.

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 description is extremely concise but at the expense of utility. It is a two-word phrase that lacks front-loaded key information. While short, it fails to provide necessary context, making it under-specified rather than efficiently concise.

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 high complexity (10 optional parameters, pagination, date filters, output schema), the description is completely inadequate. It does not explain how to use parameters, the output structure, or any constraints. The presence of an output schema does not alleviate the need for a substantive description.

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%, meaning the schema itself does not document any parameter. The description 'Get All' adds zero information about the 10 parameters (e.g., page, orderBy, start_date). An agent cannot infer how to use these parameters from the description alone.

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 vague and does not specify that the tool retrieves a list of households mealplans. It merely implies a list operation but lacks the resource context. Sibling tools like 'get_households_mealplans_by_item' indicate that this tool returns multiple items, but the description fails to clarify this distinction.

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?

No usage guidance is provided. The description does not specify when to use this tool versus alternatives such as 'get_households_mealplans_by_item' for single items or 'list_households_mealplans_rules' for related data. There is no mention of prerequisites or scenarios.

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