get_todays_meals

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

No annotations are provided, so the description carries the full behavioral burden. 'read-only' in the keyword dump hints at safety, but the description says nothing about auth requirements, household scoping, output shape, or what 'today' means in the user's timezone. For a tool with zero annotation coverage this is a real gap.

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?

Dominated by a mechanical keyword dump ('get meal plan, get meal plans, search meal plan...') that adds no informational value. Signal-to-noise is very low and the useful scoping detail is drowned in noise.

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?

For a simple zero-param read tool the description is nearly sufficient, but it omits which household the meals are pulled from (current user's household?) and how 'today' is resolved, both of which an agent needs. No output schema exists to fill the gap.

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 tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly does not invent parameter semantics.

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?

States a verb+resource ('List meal plans') and identifies the endpoint (GET /api/households/mealplans/today), but the 'today' scoping that would distinguish it from the siblings households_mealplans_get_all and households_mealplans_get_one is buried in the keyword dump rather than stated as the defining constraint. The bloated keyword list obscures rather than sharpens the purpose.

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?

No explicit when/when-not guidance. A near-identical sibling (households_mealplans_get_all) exists, and the description never says to prefer this one when the intent is 'today' rather than an arbitrary range. There is no routing information at all.

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