mealie_get_recipe

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

The verb 'Fetch' implies a non-destructive read operation, which is the main behavioral trait. However, with no annotations provided, the description does not disclose error behavior, authentication needs, or any additional constraints, leaving the agent to infer from the tool name and context.

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 with no redundant information, front-loading the core purpose and parameter semantics effectively.

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 simple one-parameter fetch tool, the description is sufficiently complete. It clearly states what it does and how to identify the recipe, and the presence of an output schema covers return values. It lacks notes on edge cases or usage scenarios, but these are not critical for this simple operation.

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 0% for the single parameter, but the description explicitly explains that the identifier can be either a slug or an id, adding meaning beyond the schema's property name 'slug_or_id'. This clarifies the parameter's accepted values.

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 'Fetch one recipe by slug or id' uses a specific verb (Fetch), resource (one recipe), and identifier (slug or id), clearly distinguishing it from sibling tools like mealie_search_recipes or mealie_get_todays_meals.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention that this is the preferred tool for retrieving a single recipe when the slug or id is known, nor does it compare it to search or list tools.

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