create_issue

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

No annotations provided, so description carries full burden. It discloses dryRun behavior (only returns metadata, no creation) and implies mutation. Missing details on rate limits or auth requirements, but adequate for a creation 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?

Description is verbose with a long example and instructions. While front-loaded with purpose, the example could be shortened. Still structured and readable, but not maximally concise.

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 high schema coverage, no output schema, description covers creation, dryRun, and required confirmation. Could mention return type but acceptable without output schema.

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% with basic descriptions. Description adds value by explaining when to use dryRun to see available users/epics, and providing context for assignee and epicKey fields beyond the 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?

Description clearly states it creates new Jira issues (Task, Sub-task, Bug, Story). It specifies the action (tạo = create) and resource (Jira issue). Distinguished from siblings like update_issue, which modifies existing issues.

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?

Explicitly states when to use: breaking down large tasks into sub-tasks or creating tasks from .md files. Also includes a mandatory instruction to ask user confirmation before calling the tool, and provides a detailed example to guide user input.

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