Find Recipes by Ingredients

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, covering safety and idempotency. The description adds that results show used/missing ingredient counts and are ranked by match, which is useful but not critical beyond the schema. No contradictions with annotations. The description does not discuss pagination, rate limits, or other behavioral aspects.

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 a single sentence of 15 words, immediately stating the verb and key outcome. It is front-loaded with 'Find recipes by ingredients', which directly conveys purpose. Every part is essential, with no redundancy or filler. Excellent conciseness.

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?

Given the presence of an output schema (not shown but indicated as true), the description need not explain return values. Annotations are thorough. The description covers the core functionality and ranking hint. However, in the context of a large server with many sibling tools, some explicit guidance on when to choose this over other recipe tools would enhance completeness. Currently, it is adequate for a simple search tool.

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?

All four parameters are fully described in the input schema (100% coverage). The description mentions 'shows used/missing ingredients count, ranked by ingredient match', which aligns with the 'ranking' parameter but adds no new information beyond the schema's parameter descriptions. Since schema coverage is high, baseline is 3; the description does not elevate it.

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 clearly states the verb 'Find recipes using ingredients you have on hand' and the resource 'recipes'. It also specifies what it shows ('used/missing ingredients count') and how results are ranked ('ranked by ingredient match'). This differentiates it from sibling tools like spoonacular.recipes.search (which likely searches by recipe name or cuisine) and spoonacular.recipes.details (which retrieves specifics for a given recipe). The purpose is unambiguous and distinctive.

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 description implies usage when the user has ingredients on hand, but it does not explicitly state when to use this tool versus alternatives like spoonacular.recipes.search or spoonacular.recipes.analyze. No prohibitions or alternative tool names are given. The context of ingredients-based search is clear, but explicit guidance would improve score.

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