create_issues

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

No annotations provided, so description carries full burden. It discloses parallelism with max_workers, return structure with success/failure per issue, and key fields. Lacks rate limit or auth details, but adds significant behavioral context.

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?

Two digestible paragraphs with clear structure: purpose, fields, options, return type. No wasted words, front-loaded with key action.

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?

Covers required fields, optional fields, parallel execution, and return format. Output schema exists so return is explained. Missing default behavior of owner/repo, but sufficient for typical use.

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 0%, but description adds meaning to all parameters: specifies issues array format (title required, body, labels, milestone, assignables) and max_workers options. Owners and repo have defaults but not explained; still strong value.

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 'Create GitHub issues (1 or more)' with a focus on parallel execution. It distinguishes from sibling tools like close_issue or list_issues by emphasizing bulk creation.

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 hints at use for bulk creation with parallelism but does not explicitly state when not to use or contrast with siblings like batch_update_issues. It provides clear context but lacks exclusions.

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