Import recipe from image

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

Annotations already indicate readOnlyHint=false and openWorldHint=true. The description adds value by explaining that the tool requires an external AI provider, that the call fails without it, and that the configuration is role-restricted. No contradiction with annotations.

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 two sentences with no wasted words. The first sentence front-loads the purpose and method, the second covers the critical prerequisite. Every sentence earns 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?

Given the tool's moderate complexity (external dependency, 3 parameters, no output schema), the description covers the purpose, prerequisite, failure mode, and role restriction. It could mention what the tool returns (e.g., a recipe ID) but is otherwise sufficient for an agent to use 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 100%, so the baseline is 3. The description mentions 'a photo' but does not add details about the base64 encoding, format, or translation parameter beyond what the schema already provides. No additional parameter-level guidance is given.

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 action ('Creates a recipe') and the resource ('from a photo'), with specific examples of inputs (cookbook page, handwritten card). It distinguishes this tool from siblings like import_recipe_from_url or create_recipe by specifying the AI-driven photo-to-recipe process.

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 explicitly mentions the prerequisite of an AI provider set up in Mealie and warns that the call fails without it. It also notes that the setting is only visible to admins/group managers. While it doesn't name specific alternative tools, it provides clear context for when to use (and not use) this tool.

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