bulk_create_issues

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

No annotations are provided, so the description carries full burden. It discloses the 50-issue limit but fails to mention atomicity, partial failure behavior, authentication requirements, or the return format. For a bulk write operation, this leaves significant behavioral gaps.

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, front-loaded sentence with no wasted words. It efficiently states the operation, resource, and a key constraint (max 50).

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 no annotations or output schema, the description is too sparse. It lacks critical context about error handling, validation semantics, and post-creation behavior. The 50-issue limit is the only extra context, which is insufficient for a complex bulk operation.

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 description does not compensate. It provides no explanation of the 'issues' array structure, required fields per item, or valid values for fields like issueType or projectKey. The parameter names alone are insufficient for an agent to construct correct input.

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 'Create multiple issues in a single request (max 50)' uses a specific verb ('create'), resource ('issues'), and scope ('multiple', 'max 50'). It clearly distinguishes itself from create_issue (single) and bulk_transition_issues (transitions, not 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 implies usage for batch creation but does not state when to prefer it over alternatives or when not to use it. No explicit exclusion or alternative mention, though sibling tools like create_issue make the use case inferable.

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