get_recipe_information

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

No annotations are provided, so the description bears full responsibility. It states 'Get detailed information' but does not disclose whether the operation is read-only, potential side effects, authentication requirements, rate limits, or error behavior (e.g., if ID is not found). This is a significant gap for a tool that likely performs a read operation.

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, clear sentence with no unnecessary words. It is front-loaded and directly conveys the tool's purpose.

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?

The tool is simple (2 parameters, no output schema, no annotations), and the description is adequate for a basic 'get by ID' pattern. However, it could be improved by mentioning the optional 'includeNutrition' parameter and briefly noting what kind of details are returned (e.g., '...including ingredients, instructions, and nutrition if requested').

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 description coverage is 100% (both 'id' and 'includeNutrition' have descriptions in the input schema). The description adds no additional meaning beyond what the schema already provides. Per the rubric, with high coverage (>80%), baseline is 3.

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 ('Get'), the resource ('detailed information about a specific recipe'), and the input method ('by ID'). It effectively distinguishes itself from sibling tools like 'search_recipes' (search, not specific) and 'get_random_recipes' (random).

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 for when you have a specific recipe ID, but it provides no explicit guidance on when to use this vs alternatives (e.g., 'search_recipes' for finding by criteria, 'find_recipes_by_ingredients' for ingredient-based lookups). No exclusions or context are given.

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