jira_bulk_edit_issues

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

Annotations declare destructiveHint=true, and description confirms 'Bulk edit fields' as a write operation. Adds context about 'All issues get the same field values set' and mentions dry_run info. No contradiction, but lacks details on permissions or overwriting behavior.

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?

Extremely concise: two sentences plus return format. Front-loaded with purpose. No wasted words.

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?

With output schema present, return values are documented. Description mentions dry_run. Covers core functionality amid many sibling tools. Sufficient for an agent to select and invoke correctly.

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 description adds value by referencing 'Same format as jira_issues_update' for fields parameter, aiding reuse. Issue_keys example is clear. send_notification default is stated. Provides meaning beyond schema.

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 'Bulk edit fields on multiple Jira issues' with specific action and resource. It distinguishes from sibling tools like jira_issues_update (single) and jira_bulk_transition_issues (bulk transition) by focusing on field editing.

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?

Provides guidance on when to use: 'For batch operations like bulk-setting labels, priorities, or custom fields.' Implicitly contrasts with single issue update. Missing explicit when-not-to-use instructions, but context from siblings fills the gap.

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