get_meals

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

With no annotations, the description carries the behavioral burden. It discloses the fallback behavior between the personal endpoint and public widget, default returned meals, and the constraint that extra meals are only available through the public widget. Authentication and return format are not covered, but the read-only nature 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?

Three sentences cover the defaults, endpoint fallback, and parameter behavior without filler or redundant schema repetition. The most important usage information is front-loaded.

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?

The description provides the key invocation knowledge: default date, returned meal categories, optional expansion flags, and fallback endpoint behavior. It omits return shape and auth preconditions, but those are less critical given the fully optional parameter set.

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 provides no parameter descriptions, and the description compensates well for date_str and include_breakfast/include_dinner. However, subdomain is never explained and the expected date format is left unspecified, so the coverage is good but incomplete.

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 names a concrete read operation: get the meal menu for a date, and lists the meal categories and default date. It also distinguishes itself from action-focused sibling tools like choose_meal, sign_off_meal, and rate_meal.

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?

It explains default usage, how to extend with include_breakfast/include_dinner, and when the public fallback endpoint is used. It does not explicitly cross-reference sibling tools or state when not to use them, but the usage context is clear.

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