taiga_bulk_create_stories

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

With no annotations, the description carries the full burden. It usefully discloses the required item shape and the epic_id prerequisite, but for a bulk mutation tool it omits behavior that matters most: atomicity/partial-failure semantics, whether epic linkage is required or optional, and what happens if one story in the batch is 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?

Two sentences, zero filler, with the per-story requirement and the blocking epic_id caveat both front-loaded. Efficient, though the capitalized warning eats space that could have covered failure behavior.

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?

Placeholder.

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 only 25%, and the description does add real meaning beyond the schema: the required inner 'subject', the optional 'description' and 'tags', and the numeric-vs-ref caveat on epic_id. However, sprint_id and project_id are undocumented in both schema and description, leaving a genuine compensation gap.

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?

States a specific verb and resource ('Create multiple user stories') and the required per-item field ('subject'), so it is distinguishable from taiga_create_user_story by the 'multiple' framing. It never explicitly contrasts with the single-create sibling, so it stops short of a 5.

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 prerequisite workflow for one parameter: call taiga_list_epics first to obtain epic_id, and warns against using ref #. It says nothing about when to choose bulk creation over calling taiga_create_user_story repeatedly, nor when to supply sprint_id.

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