Import recipe from URL

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

Beyond the annotations, the description discloses that fetching happens on the Mealie server, which has network and permission implications. It also warns that 'everything the page contains... ends up in the collection as written by whoever controls that site,' revealing that imported content is not sanitized or curated. This adds meaningful behavioral 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 three sentences and each one earns its place: first the primary action, second the server-side execution boundary, third the scope of imported content and its source-controlled nature. It is front-loaded and contains no fluff or repetition.

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 relatively simple import tool with no output schema, the description sufficiently covers the purpose, the execution environment, and what content will be saved. It does not explicitly mention return values or failure behavior, but the annotations and input schema already convey safety and parameter requirements, so the description is reasonably complete.

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 67%: url and include_tags are documented, but include_categories has no schema description and the tool description does not clarify it. The description adds general context about what content gets imported, but it does not enrich the semantics of the individual parameters beyond what the schema already provides.

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 a specific action and resource: 'Has Mealie fetch a recipe page and save it as a new recipe.' This distinguishes it from siblings like preview_recipe_url and import_recipe_from_html_or_json by emphasizing URL-based, server-side import. The scope is concrete and unambiguous.

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?

It gives clear context for when to use the tool: when you want Mealie itself to fetch a remote recipe page, and the phrase 'not here' sets an important boundary about where the fetch occurs. However, it does not explicitly name alternatives or state when not to use this tool versus import_recipe_from_html_or_json or import_recipe_from_image.

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