get_recipe

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about permissions (group membership), return shape, or error behavior. The only signals are the 'read-only' keyword and the GET endpoint path, which are weak and indirect.

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?

Roughly half the text is a bloated keyword dump ('get_recipe, get recipe, fetch recipe, read recipe... mealie') that repeats the name and adds no meaning. The single substantive sentence is a tautology, so every sentence after 'Get Recipe' fails to earn its place.

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?

With no annotations, no output schema, 0% parameter coverage, and a crowded sibling set, the description needs to do heavy lifting but supplies none of the required context for correct invocation.

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 0% for both required params. The endpoint template implies group_slug and recipe_slug are path segments, but the description never states their format, source, or constraints, so the schema gap is not compensated.

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 operative sentence is 'Get recipe,' a tautological restatement of the tool name. The endpoint template and 'Explore: Recipes' hint at a group-scoped recipe fetch, but nothing distinguishes it from the very similar sibling recipe_crud_get_one or get_shared_recipe, so an agent cannot tell which fetch to pick.

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, when-not-to-use, or alternative is stated. The keyword tail (get, fetch, read, retrieve, view, show) is search-synonym noise, not guidance, and it actively obscures rather than routes among the many sibling 'get recipe'-like tools.

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