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

Goes well beyond readOnlyHint/openWorldHint: it discloses that the saved pantry is the default input, that staples are assumed, and that allergies, diet and avoid-list are silently applied — all things an agent must know to interpret results honestly. It also tells the agent how to present results (top few, have/missing line, url). It stops short of covering empty-result or limit behavior, so not a 5.

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?

Dense but front-loaded — the ranking premise and the output shape come first, then usage triggers, then parameter guidance. Every clause carries information, though the parenthetical example sentence is slightly long for what it adds.

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?

An output schema exists, so return values needn't be spelled out; the description still adds the one thing the schema can't — how to read and present the have/missing line. Combined with the pantry/allergy/staples semantics, an agent has everything needed to call this correctly and interpret the result.

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 only 50%, and the description compensates for most of it: pantry is explained as a signed-out/what-if override, must_use as hard requirements, query as keywords, plus tags and max_minutes as narrowing filters. Only 'limit' is left to the schema, which is acceptable given its default.

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 specific verb+resource (recipes ranked by pantry coverage) and immediately differentiates itself from a plain keyword search by describing the have/missing line output. An agent can tell this apart from search_recipes or build_shopping_list without opening a schema.

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?

Gives explicit trigger phrases ('what can I make?', 'what can I do with chicken and rice?'), a named mode (must_use for 'the chicken has to get used tonight'), and the exact condition for overriding the saved pantry ('signed out, or for what if I had…, pass pantry'). It also routes the follow-up ('a list of just the missing items is the natural next step'), which points at the shopping-list sibling.

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