get_custom_recipe

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

No annotations are provided, so the description carries the full burden. The verb 'liest' implies a read operation, and the description specifies the content (ingredients, steps, annotations), which is helpful. However, it does not disclose side effects, error handling, or permission requirements, leaving some behavioral aspects unclear.

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 concise sentence that immediately communicates the tool's purpose without any unnecessary detail or repetition. It is front-loaded and easy to parse.

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 tool's simplicity and the presence of an output schema, the description covers the core behavior and content. However, it lacks usage context regarding when to choose it over sibling tools like get_recipe_details, and it does not address potential edge cases, making it only partially complete for an agent selecting the appropriate 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?

The schema has 0% description coverage for the single parameter 'recipe_id', and the description does not explicitly explain how to use it. While the parameter name is self-explanatory and the description implies reading a specific recipe, it does not add explicit meaning beyond the schema's structural definition.

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 it reads a custom recipe with ingredients, steps, and annotations. It uses a specific verb 'liest' (reads) and resource 'Custom-Rezept' (custom recipe), which distinguishes it from sibling tools like list_custom_recipes (listing) and get_recipe_details (which likely covers standard recipes, not custom ones).

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?

There is no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios where other tools like get_recipe_details or list_custom_recipes would be more appropriate.

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