jira_batch_create_issues

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

With no annotations, the description should disclose key behaviors. It mentions the max-50 constraint but omits critical details like all-or-nothing semantics, partial success handling, rate limits, or authentication needs.

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 extremely concise at one sentence. It conveys the core purpose and constraint without filler, placing critical information upfront.

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 batch operations and no output schema, the description lacks information on error responses, partial failures, or transaction guarantees. Users cannot predict the outcome of a mixed-success batch.

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 100%, so the description adds little beyond the schema. The max-50 constraint for the array is noted, but it does not clarify whether 'additionalFields' support required fields or override logic.

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 multiple Jira issues' and the constraint 'max 50'. It effectively distinguishes this batch tool from the single-issue sibling 'jira_create_issue'.

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 batch use but does not explicitly guide when to choose this tool over 'jira_create_issue' or mention any preconditions (e.g., required permissions). Usage context is implied but not explicit.

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