Import several recipes from URLs

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the mutation/network profile is covered. The description adds genuinely new behavior: the 15-item cap, per-URL failure semantics ('reported, not thrown'), and the favorite side-effect. It omits rate-limit/partial-success nuance, keeping it just below 5.

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?

Three tight sentences, front-loaded with the core purpose before the usage scenario and the input-prep instruction. No filler, though the 'Names without URLs are your job' sentence is slightly oblique relative to the schema, which requires a URL.

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?

An output schema exists, so return-value documentation is unnecessary; the description still covers the important failure-mode contract (per-URL failures reported, not thrown). Combined with the 15-item cap and favorite behavior, an agent has enough to call it correctly, with only the tags parameter left unaddressed.

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 50%, and the description only touches 'favorite' (via 'marking each as a favorite') and the URL requirement; it says nothing about the 'tags' field or the 'favorite_all' toggle. The baseline of 3 for partial coverage is appropriate since the schema still carries most parameter meaning.

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?

Opens with a specific verb+resource ('Bulk version of import_recipe: fetch up to 15 recipe pages and save them to the library') and explicitly distinguishes itself from the singular sibling import_recipe. An agent can tell immediately what this does and how it differs from import_recipe.

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?

Gives a concrete use case ('when the owner is moving favorites from another app') and a prerequisite workflow (search for a real recipe page first when only a name is given). It does not state when NOT to use it (e.g., single-recipe case -> import_recipe), so it falls short of the top band.

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