plan_and_shop

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

Describes the return structure (meal plan day-by-day with costs, deal-optimized shopping list grouped by store). No annotations exist, so description carries the burden; it could explicitly state if the plan is saved or if it's read-only, but it sufficiently communicates the main outcomes.

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?

Three sentences front-loading the core purpose, then usage guidance, then return details. No wasted words; each sentence adds unique value.

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?

No output schema but the description explains the return format. Covers main inputs, but lacks details on error handling or edge cases. Given complexity (8 params, nested objects), it is mostly complete.

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 100% with each parameter fully described. The description does not add additional semantic value beyond the schema, so baseline 3 is appropriate.

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 the tool scores recipes, optimizes a weekly meal plan, and generates a shopping list in one step. Provides example usage phrases like 'plan my week' and distinguishes itself from generate_shopping_list.

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 states 'USE WHEN' with specific queries and 'NOT FOR' with an alternative sibling tool (generate_shopping_list), giving clear guidance on when to invoke this tool vs others.

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