submit_bulk_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. "Bulk delete" conveys destructiveness but says nothing about whether deletion is permanent, whether notifications are sent, what permissions are required, or what response is returned.

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 and front-loaded with the core action. It does not waste words, but it is so terse that it leaves out behavioral and usage context.

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?

For a destructive bulk operation with no annotations and no output schema, a three-word description is not enough. It lacks details on effects, prerequisites, response behavior, and how it differs from related tools.

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% for the body parameter, so the schema already explains the request body. The tool description itself adds no parameter-level meaning, but the nested property names like selectedIssueIdsOrKeys and sendBulkNotification are reasonably self-explanatory.

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?

"Bulk delete issues" clearly states the verb and resource. It distinguishes itself from sibling bulk operations like submit_bulk_move or submit_bulk_edit, though it does not explicitly contrast with the single-issue delete_issue tool.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that delete_issue might handle single deletions or that bulk operations are for multiple issues, leaving the agent to infer usage context.

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