update_issue

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

Discloses dryRun behavior for safe preview, ability to combine multiple changes, fuzzy match for assignee, and the need for user confirmation. No annotations exist, so description carries the burden well.

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?

Front-loaded with purpose, then uses bullet-like explanation for each field, ending with a warning. Slightly verbose in Vietnamese but well-structured and essential.

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?

Thoroughly covers all operations, combination rules, and safety requirements. No output schema but return values are obvious for a mutation tool. Complete enough for an agent to use 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?

Adds significant meaning beyond input schema: 'unassigned' for removing assignee, 'clear' for due date, comment independence, fuzzy match support. Schema coverage is 100% but description enriches understanding.

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 updates Jira issues with specific actions: assign/unassign, change status, add comment, view transitions. Distinguishes from sibling tools like create_issue and list_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?

Provides clear guidance on when to use dryRun, how to assign/unassign, change due date, add comment, and combine actions. Includes a required user confirmation warning but lacks explicit when-not-to-use compared to siblings.

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