bulk_tag_recipes

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

With no annotations, the description must convey behavioral traits like mutability, idempotency, permissions, or side effects. The description only repeats the name and endpoint, offering no insight into whether tags are appended or overwritten, or what happens if recipes or tags are invalid.

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?

At 10 words, the description is extremely concise but sacrifices all substantive information. It fails to front-load key details about the operation or parameters. Every sentence should add value, but this one merely restates the tool name.

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?

The tool has a complex input schema with a nested object, no output schema, and no annotations. The description does not cover return values, error handling, or prerequisites (e.g., authentication, recipe existence). For a bulk mutation tool, this is critically insufficient.

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%, so the description should explain the parameters. It does not mention that 'body' requires 'recipes' (array of recipe IDs) and 'tags' (array of tag objects with id, name, slug). The agent must infer from the schema alone, which lacks descriptions.

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 'Bulk Tag Recipes' combined with the endpoint path '/api/recipes/bulk-actions/tag' clearly indicates the tool is for tagging multiple recipes in bulk. It distinguishes from sibling tools like 'bulk_categorize_recipes' or 'delete_recipe_tag'. However, it does not clarify whether tags are added or replaced, leaving some ambiguity.

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 guidance is provided on when to use this tool versus alternatives such as 'organizer_tags_create_one', 'delete_recipe_tag', or other bulk actions. There is no mention of prerequisites, context, or exclusions.

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