skylight_list_meals

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

With no annotations provided, the description carries the transparency burden. It discloses the shape of the listing by explaining that each sitting carries `instances`, `meal_category`, `meal_recipe`, and `profiles`, and it implies a read-only operation via 'List'. It does not cover pagination or ordering, but the core behavior is clear.

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?

Two dense sentences with no filler. The first sentence states purpose and scope; the second explains what the returned sittings contain. Every sentence earns its place.

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?

There is no output schema, so the description should compensate by explaining return values, and it does: it enumerates `instances`, `meal_category`, `meal_recipe`, and `profiles`, including the breakfast/lunch/dinner domain. The optional `frameId` behavior is absent, but the core date-range listing scenario is sufficiently documented.

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 already documents `date_min` and `date_max` with format and inclusivity, so the description adds little beyond echoing the date-range concept. The optional `frameId` parameter has no schema description and is not explained in the tool description either, leaving a real gap for agents.

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?

Description uses a specific verb ('List') plus a concrete resource ('planned meals / meal sittings') and clearly scopes it to a date range. It also distinguishes the tool from siblings like `skylight_plan_meal`, `skylight_generate_meal_plan`, and `skylight_list_meal_categories` by describing what actually gets returned.

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 establishes a clear usage context: query the meal plan for a date range and see what is assigned to each day. It does not explicitly name alternatives or state when not to use it, but the read-only listing purpose is unambiguous.

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