jira_issues_bulk_create

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

Description discloses creation action and return format with {created: [{key, id}], errors: [...]}. Annotations already indicate non-readOnly and non-idempotent, so description adds useful context about response structure.

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?

Three concise sentences front-load purpose and limit, with no unnecessary words. Every sentence adds value.

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 tool's complexity (single parameter with nested object) and presence of an output schema, the description covers required fields, optional fields, limits, and return format comprehensively.

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% but description adds meaning by listing required and optional fields (project_key, issue_type, summary, etc.) within each issue, clarifying the structure of the issues array.

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?

Description clearly states the verb 'create' and resource 'multiple Jira issues', with a limit of 50. It distinguishes from sibling tools like jira_issues_create (single issue) and bulk edit/transition.

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?

Specifies maximum count (up to 50) and required minimum fields (project_key, issue_type, summary). Implies use when creating multiple issues at once, but does not explicitly state when to avoid or list alternative tools.

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