Get Meal Plan Week

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful scope information - the fixed 7-day window and the today default - but says nothing about whether days without entries are returned, timezone handling, or ordering.

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?

A single sentence with no waste: the action, the resource, the window length, and the default are all front-loaded. Nothing could be removed without losing information.

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 one-optional-parameter read tool with an output schema, this is nearly complete - the agent knows what is returned and over what range. The only residual gaps are formatting concerns like ordering and handling of empty days, which are secondary.

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%, so the baseline is 3. The description goes slightly beyond the schema by explaining that the date is the *first* day of a 7-day window and that the effective default is today (the schema only shows default null), which resolves how null behaves.

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 specific verb ('Show') and resource ('the meal plan') and scopes it to 'the 7 days starting at a day', which clearly separates it from sibling mutators like add_to_meal_plan or move_in_meal_plan. It stops short of explicitly naming a sibling alternative, so it is clear but not maximally differentiated.

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?

Read semantics are implied by 'Show', and the default of today is stated, which gives an agent enough to act. There is no explicit when-to-use versus alternatives or any stated exclusions (e.g., use get_shopping_list for ingredients).

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