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

The annotations already declare read-only, idempotent, non-destructive behavior, and the description reinforces that with 'Read-only; saves nothing.' More importantly, it discloses the workflow states, return shape, and how to present results, which goes well beyond the annotations.

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 description is dense but front-loaded: what it does first, then read-only behavior, then return structure and presentation guidance, then next-step routing. No sentence is wasted.

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?

Although there is no output schema, the description supplies the return shape and the saved flag needed to choose the next tool. For a one-parameter brainstorming tool, this is sufficient for correct invocation and follow-up.

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%, and the single category parameter is already well documented with examples. The description's parenthetical about cuisine, theme, occasion, and flavor adds some nuance, but the schema still carries most of the parameter meaning.

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 states a specific verb and resource: 'Brainstorm dishes for a vague idea.' It also distinguishes the tool from recipe lookup and drafting tools by explaining its exploratory role and naming the follow-up tools.

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 explicitly says when to use it: for a vague idea involving cuisine, theme, occasion, or flavor. It also gives clear post-selection routing: use start_recipe_draft for a new dish, or get_recipe if the result is already saved.

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