plan_week

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

No annotations provided, so description carries full burden. Explains key behaviors: saves as current plan, reuses leftovers, avoids recently-cooked recipes, optimizes overlap and diversity. Does not mention overwriting behavior but implies it.

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?

Well-structured with clear paragraphs, front-loads main purpose. Detailed but not verbose. Could be slightly more concise but effective.

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?

Tool has 9 parameters, no output schema, no annotations. Description leaves many parameters unexplained (7/9). No mention of return value or success behavior.

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 coverage is 0%. Only main_course_only and diversity_weight are explained in detail. Other 7 parameters (days, max_time, start_date, exclude_tags, include_tags, household_size, avoid_recent_days) are not described.

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?

Clearly states 'Build and save a meal plan' with specific optimization goals (ingredient overlap, leftovers). Distinguishes from sibling tools like swap_meal, remove_meal, generate_shopping_list, export_plan.

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?

Explicitly describes when to use (build and save a meal plan) and mentions alternatives for tweaking (swap_meal, remove_meal) or re-calling. Lacks explicit 'when not to use' but context is clear.

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