skylight_generate_meal_plan

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

Discloses async nature and draft creation, which are key behavioral traits. With no annotations, description carries full burden; rate limits or destructive potential not mentioned, but core behavior is well covered.

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?

Single sentence packed with essential info: action, resource, async nature, follow-up steps. Front-loaded, no filler.

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, description omits return value (e.g., what intent ID or confirmation). Provides polling tool name but incomplete for an async tool without return specification.

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 67% (4/6 parameters described). Description does not add extra meaning beyond schema; undocumented parameters (frameId, add_to_grocery_list) not addressed. Baseline 3 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 generates an AI meal plan for given dates, distinguishes from siblings by noting it's async and requires polling and approval, which is specific and unique among similar tools.

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 instructs to poll with skylight_get_auto_creation_intent then approve, providing clear context for async workflow. Lacks explicit when-not-to-use or comparison with sibling tools like skylight_plan_meal, but sufficient.

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