List Households Mealplans

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

No annotations are provided, so the description must carry behavioral disclosure, but 'Get All' reveals nothing about pagination defaults, date filtering semantics, ordering behavior, or that this may return a large collection. It does not disclose side effects (though listing is likely read-only, it is not stated) nor any rate/visibility constraints.

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?

'Get All' is under-specified rather than concise. It has no front-loaded detail, no clarification of scope, and every word is generic, so the sentence does not earn its place.

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?

The presence of an output schema and zero required parameters reduces some burden, but a 10-parameter listing tool with no description of filtering, pagination, or selection criteria is incomplete. The agent cannot determine how to construct a correct call beyond guessing from parameter names.

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%, so the description must compensate, but it adds zero semantic value to the 10 parameters. The date range, ordering, and pagination fields remain opaque; the agent must infer their meaning from names 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 a vague shorthand that merely restates the list nature of the name and fails to specify what resource is fetched. It does not distinguish this from sibling list tools like list_households_mealplans_rules or list_households_mealplans_today.

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 guidance is given about when to use this tool versus the many sibling mealplan tools. There is no mention of required auth/context, relationship to create/get/update/delete mealplan tools, or when a more specific endpoint like list_households_mealplans_today would be preferable.

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