Batch Create Issues

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

Annotations declare destructiveHint: true, confirming write behavior. The description adds context: read-only mode check, Jira client availability, and error handling (ValueError for invalid JSON). It also describes return format (JSON string with success/validation result). This goes beyond the annotations, though it omits details like partial batch failure handling.

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 sentences plus structured Args/Returns/Raises sections. It is front-loaded with the purpose and uses clear formatting. No redundant information, but it could be slightly tighter by merging some details.

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?

The description covers core purpose, parameters, and errors. However, it lacks transactional semantics (e.g., whether all issues are created atomically or partially), rate limits, or permission requirements. For a batch mutation tool, this missing context reduces completeness given the tool's complexity.

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 baseline is 3. The description adds minimal value beyond the schema: it reiterates that issues is a JSON array string and mentions validate_only, but the schema already provides full documentation, including an example for issues.

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 tool's purpose: 'Create multiple Jira issues in a batch.' It uses a specific verb ('Create') and resource ('multiple Jira issues'), and the batch nature distinguishes it from the sibling tool 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 does not explicitly state when to use batch versus singular creation. While the name and context imply the batch variant, there is no guidance on trade-offs, alternatives (e.g., jira_create_issue), or when validate_only should be used. The usage is implied but not articulated.

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