households_mealplans_get_all

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

No annotations are provided, so the description must convey behavioral traits. It only implies a read operation via 'Get' and the GET endpoint, but does not disclose pagination behavior, return format, or any side effects. Minimal transparency.

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 brief ('Get All' and endpoint), but this is under-specification rather than efficient conciseness. Structure is minimal and lacks any helpful sections.

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 tool complexity (9 parameters, no output schema, many siblings), the description is severely incomplete. It fails to explain the purpose, parameters, or behavior, leaving the agent with insufficient context to use the tool effectively.

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?

The input schema has 9 parameters with 0% description coverage, and the tool description adds no information about their meaning or usage. The agent cannot infer how to use parameters like page, perPage, start_date, end_date, etc.

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 of the tool name and provides no additional clarity about what resource is being retrieved. The endpoint path is mentioned, but it doesn't specify that it retrieves all mealplans for a household, nor does it distinguish from sibling tools like households_mealplans_get_one.

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?

The description offers no guidance on when to use this tool versus alternatives such as households_mealplans_get_one or other list tools. No context about filtering, pagination, or use cases is provided.

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