Batch Create Issues

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

Description states the core action but does not disclose batch-specific behaviors such as validation-only mode (validate_only parameter), partial success handling, or concurrency implications. Annotations only provide destructiveHint=false, which is consistent but doesn't add further context.

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?

One sentence, zero redundancy. However, while concise, it omits any usage guidance that could be included in a similarly short form.

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 batch creation tool with a validate_only option and potential partial failures, the description is insufficiently complete. It doesn't mention the validation feature or how batch creation contrasts with single-issue creation, leaving the agent without key context.

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?

Input schema describes both parameters in detail, including an example for the issues array and default for validate_only. The description adds no parameter information, but the schema's high coverage means the baseline of 3 applies.

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 uses the specific verb 'Create' with the resource 'multiple Jira issues' and 'batch', clearly distinguishing from single-issue creation (jira_create_issue) and batch version creation (jira_batch_create_versions).

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 explicit guidance on when to use this tool vs alternatives. The sibling list includes jira_create_issue for single issues, but the description doesn't direct users to choose one over the other, nor mention any prerequisites or use cases.

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