taiga_epics_related_userstories_bulk_create

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

With no annotations provided, the description must carry the burden of disclosing behavior. It only says 'bulk add', which implies mutation, but does not reveal that new user stories are likely created (based on 'subjects'), whether the operation is atomic, or what happens on partial failure. No side effects are disclosed.

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 a single, concise sentence with no filler. It is easy to parse and front-loaded with the action.

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 simple 3-parameter tool with full schema coverage and no output schema, the description is minimally adequate. However, it lacks context about the creation behavior and the effect on the epic, which is important for an agent deciding whether to invoke this tool. It does not explain the return value or any prerequisites.

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 100%, so the schema documents all parameters well. The description adds the concept of 'bulk' and 'epic' but does not add meaning beyond what is already in the parameter descriptions. Baseline 3 is appropriate.

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?

'Bulk add user stories to an epic' clearly identifies the action (bulk add) and resource (user stories to an epic). It distinguishes from the singular 'related_userstories_add' sibling, but does not clarify whether the user stories already exist or are being created, 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?

The description provides no guidance on when to use this tool versus alternatives like the singular add tool. It does not state that it is for creating new user stories in bulk or that it should be preferred over individual adds. No context or exclusions are given.

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