explore_recipes_suggest_recipes

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

Annotations are absent, so the description carries the full burden and it fails. It never says this is a read-only operation, never explains that results must be scoped to a group_slug, never mentions whether results are ranked or personalized, and gives no pagination or result-size context despite an explicit limit/paginationSeed pair.

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?

Severely bloated: the bulk of the text is an alphabetical synonym flood (list/post/g/l/i/k) that would have been better replaced by one real sentence, while a raw URL path is front-loaded as if it were user-facing documentation.

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 13-parameter, no-annotation, no-output-schema tool, the description omits required group_slug semantics, the food/tool matching model, the missing-count thresholds, ordering, and result shape. It cannot be called correctly from this definition alone.

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?

13 parameters with 0% schema description coverage, and the description mentions none of them. Ten of them (foods, tools, maxMissingFoods, maxMissingTools, includeFoodsOnHand, includeToolsOnHand, orderBy, orderDirection, orderByNullPosition, paginationSeed, queryFilter) are bare titles in the schema with no meaning attached anywhere, so an agent has no basis for setting the suggestion-ranking knobs.

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 meaningful content is 'Suggest Recipes — Explore: Recipes. List suggestions' plus a raw REST path. That restates the name rather than stating what a 'suggestion' is or how it differs from the siblings recipe_crud_suggest_recipes and explore_recipes_get_all. The keyword tail then lists generic synonyms (list, get, search, find) that add no discriminating information.

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?

No when-to-use guidance at all, and no mention of the two obvious alternatives for the same job: recipe_crud_suggest_recipes and explore_recipes_get_all. The synonym dump actually encourages wrong selection by implying the tool is a generic search/find endpoint.

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