Batch Create Issues

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

The description adds critical behavioral details beyond the annotations: it reveals that items are created independently (a bad item doesn't fail the batch) and that the return is a structured per-item success/failure result. These are not encoded in the readOnly/destructive/idempotent hints and significantly aid agent understanding.

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 three concise sentences, each serving a clear purpose: the first announces the action, the second explains the independence behavior, and the third describes the return format and contrasts with an alternative. It's front-loaded and free of extraneous detail.

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?

Given the complexity of a batch endpoint with nested items, the description covers the essential limits (up to 20), per-item independence, and return structure. The schema provides the required field details, so the description needn't repeat them. However, it could have mentioned the required fields or given an example, but the structured schema fills that gap.

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?

The tool description provides almost no parameter-level guidance. It mentions the 20-issue limit but doesn't explain the `project` parameter or the required fields (`subject`, `type`, `priority`, `severity`) within `items`. Since schema coverage is 0%, the description fails to compensate for the lack of schema 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 clearly states the action ('Create') and resource ('up to 20 issues'), making it obvious this is a batch creation tool. The mention of per-item fields distinguishes it from native Taiga bulk-create and implies differentiation from single-issue creation.

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 explicitly contrasts this tool with the native Taiga bulk-create, explaining when this tool is preferable (when per-item fields are needed). However, it doesn't mention when to use this over single-issue creation or other batch tools, though the tool name and sibling context imply the use case.

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