mealie_upload_recipe_asset

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

There are no annotations, so the description must disclose behavior. It reveals that the upload uses multipart and targets an existing recipe, but it does not explain side effects, required permissions, overwrite behavior, or failure modes. The term 'real file asset' hints that it expects actual file data, but lacks depth.

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 sentence, front-loaded with the key action and target. Every word contributes to clarity, with no redundant information.

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 five parameters, zero schema descriptions, and no annotations, this one-sentence description is insufficient. It doesn't explain how to construct the multipart request, what the parameters mean, or what the expected response is. An agent would struggle to use this tool correctly.

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%, yet the description does not explain any parameters. It implies slug_or_id identifies the recipe and asset_source is the file, but asset_name, icon, and confirmed_by_user remain unexplained. This leaves the agent guessing about required formats and semantics.

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 uses a specific verb 'Upload' and identifies the resource as 'a real file asset to an existing recipe via multipart.' This clearly states the tool's function and distinguishes it from sibling tools like mealie_update_recipe_image which targets images specifically.

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 usage guidance is provided. The description does not mention when to prefer this over alternatives (e.g., mealie_update_recipe_image) or any prerequisites. The only implied usage is for uploading file assets to recipes.

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