create_issues_bulk

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the max-50 limit, but does not describe permissions, atomicity, partial-failure behavior, rate limits, or other operational traits important for a bulk mutation tool.

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 front-loaded with the core action and cap, then uses a compact Args section to enumerate field requirements. Every sentence adds useful information with no repetition or filler.

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?

An output schema exists, so return values need not be explained. However, for a bulk mutation with no annotations, the description omits important operational context such as permission needs, validation failure behavior, and whether the batch is atomic.

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 0% and the single issues parameter is an array of free-form objects. The description compensates by naming the required fields (project, issue_type, summary) and listing optional fields, giving the agent actionable parameter semantics.

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 states a specific verb and resource: 'Create multiple issues in bulk (max 50 per request).' It clearly distinguishes itself from the singular sibling create_issue by emphasizing multiple issues and a 50-item cap.

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 implies usage for bulk creation and gives a concrete capacity limit, but it does not explicitly say when to use this instead of create_issue or what alternatives exist for different batch sizes. No exclusions or prerequisites are stated.

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