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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: it works backward from serve_time, applies a default date of 26 November 2026 4:00 PM, detects oven conflicts, moves make-ahead dishes earlier, pulls turkey roast/thaw steps from the USDA table, caps input at 25 dishes, and states it does not invent times or supply recipes. It also discloses the three return artifacts (PDF, ICS with per-step reminders, shopping-day note).

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?

The trigger condition is front-loaded and the paragraph reads as a dense chain of behavioral facts with no filler sentences. It is long, but for a 17-parameter tool nearly every clause carries information; only the repeated dishes/text fallback guidance overlaps with the schema.

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 17-parameter, no-required-param tool with an output schema, the description covers the trigger, the input conversion strategy, key defaults, conflict-handling logic, limits, and what artifacts are produced. An agent has everything needed to decide to call it and how to shape inputs correctly.

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, but the description adds cross-parameter meaning the schema cannot express: it instructs converting a menu or photo into the dishes array with text as fallback only, and clarifies 'one oven by default, ovens: 2 for two'. It does not elaborate on the many numeric tuning params (hold_minutes, share_within_f), which the schema already documents.

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 opens with a concrete trigger ('Use this when the user wants a Thanksgiving cooking timeline, a holiday dinner cooking schedule or an oven schedule for several dishes'), naming a specific verb and resource. It never mentions the sibling calculate_turkey_times, so an agent cannot tell from this text alone whether turkey timing belongs here or in the sibling, keeping it below a 5.

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 gives explicit usage context via the 'Use this when...' clause and enumerates valid inputs (menu, pasted recipe notes, photo of a menu, with text only as fallback). It does not state when NOT to use it or point to calculate_turkey_times, so the guidance is clear but has no exclusions or alternatives.

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