jira_batch_create_issues

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

With no annotations, the description carries the burden and does well: it discloses the return format, validation mode, and error conditions (ValueError for read-only mode, unavailable client, invalid input). It could mention atomicity or partial-failure behavior, but what's included is solid.

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 well-structured with Args, Returns, and Raises sections, front-loaded with the core purpose. Every section earns its place, and there is no redundant or vague wording.

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 inputs, return behavior, validation mode, and error conditions, making it self-sufficient despite no annotations. An output schema exists, so the return explanation is an extra bonus, not a requirement.

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%, and the schema already provides detailed parameter descriptions including an example. The description adds only the 'ctx' argument (FastMCP context), which is a technical framework detail rather than a user-facing semantic improvement, so it stays at baseline.

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 immediately states 'Create multiple Jira issues in a batch,' which is a specific verb-resource-scope statement. This clearly distinguishes it from sibling single-create tool jira_create_issue, and the mention of 'validate_only' further clarifies its dual purpose.

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 batch nature and 'multiple' explicitly signal when this tool is appropriate, and the validate_only flag adds context for validation-only usage. It does not explicitly name alternatives or exclusions, but the contrast to a single-create sibling is implied.

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