bulk_tag_recipes

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

No annotations are provided, so the description carries the full burden, yet it discloses only that this is a POST to /api/recipes/bulk-actions/tag. It says nothing about whether tags must pre-exist, how duplicates are handled, whether assignment is additive or replacing, or permission requirements.

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 dominated by a long comma-separated keyword-stuffing block ('bulk_tag_recipes, bulk tag recipes, create tag, add tag, new tag, make tag, write tag...') that adds no semantic value. Front-loaded header is present but buried under noise.

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, and 0% parameter coverage, the description should compensate heavily. Instead it omits the request body structure, tag/recipe semantics, and any return or error behavior, leaving the definition inadequate 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% and the single 'body' parameter is a nested AssignTags object with required 'tags' and 'recipes' arrays. The description provides no explanation of these fields, adding no meaning beyond the bare schema, so an agent cannot learn the required shape from the text.

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 name 'bulk_tag_recipes' and the header 'Bulk Tag Recipes' convey a bulk tagging operation, which is close to the schema's AssignTags (recipes + tags) intent. However, the body text 'Create tag' is imprecise and mildly misleading — the endpoint assigns existing tags to recipes rather than creating a tag. No differentiation from siblings like bulk_categorize_recipes or organizer_tags_create_one.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives despite many nearby siblings (bulk_categorize_recipes, bulk_settings_recipes, delete_recipe_tag). The tool name implies bulk tagging but the description never states the conditions that select it.

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