list_households_mealplans_today

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

With no annotations and a bare description, the behavioral traits are entirely missing. The description does not disclose whether the operation is read-only, what data it returns, or any side effects.

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 but fails to convey essential information. It is not appropriately sized for the tool's complexity; it is under-specified rather than 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 tool's apparent purpose (listing today's meals within a household context), with no output schema and no description of return structure, the description is completely inadequate.

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 schema has one optional parameter (accept-language) with 0% description coverage, and the tool description does not mention or explain this parameter. The description adds no value to understanding the parameter's purpose or usage.

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 Todays Meals' is vague. It does not specify what resource is being retrieved (meal plans, meals, from which household) or how it differs from sibling tools like list_households_mealplans.

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 provided on when to use this tool versus alternatives. No context about filtering, prerequisites, or expected results is given.

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