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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering side-effect safety and use of external knowledge. The description adds valuable context by specifying the exact structure of the generated recipe, which helps the agent anticipate the tool's output beyond what annotations express.

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, well-structured sentence that front-loads the key input context (ingredients, optional restrictions) before listing the output components. There is no redundant or filler content, making it easy for an agent to parse quickly.

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 two-parameter generative tool with read-only and open-world annotations, the description covers inputs, optional constraints, and output structure sufficiently. The only gap is that it does not state whether the recipe is returned as plain text or structured data, and no output schema exists to fill that 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 schema documents 'ingredients' with format guidance, but the dietaryPreferences object has no description beyond its property names. The description's mention of 'optional dietary restrictions' partially compensates for this 50% schema coverage, but it does not explain how preferences affect recipe generation or whether only the listed booleans are supported.

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 uses a specific verb and resource combination ('generate a complete recipe') and enumerates the concrete output components: name, servings, timing, ingredient list, and steps. This clearly states what the tool does and leaves no ambiguity about its function.

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 opening phrase 'Given ingredients on hand (and optional dietary restrictions)' provides a clear context for when to call the tool. Since there are no sibling tools, there are no alternatives to exclude, so the absence of explicit when-not guidance is acceptable.

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