Assign Jira Issue

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only says 'Assign issue to user' without mentioning effects like overwriting existing assignee, required permissions, or error behavior for invalid issue/user, so it fails to provide necessary transparency.

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 a clean, front-loaded single sentence with no filler. It is concise and easy to parse, though it could be slightly expanded with behavioral or usage context without harming conciseness.

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 mutation tool with no annotations and no output schema, the description is too sparse. It omits details about how the assignment behaves (e.g., whether prior assignee is replaced), permission requirements, error cases, and expected outcomes. This is insufficient for an agent to confidently use the tool 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?

The input schema has 0% description coverage, and the description does not compensate. It merely paraphrases 'issue' and 'user' without explaining the issueKey format, username type (e.g., display name vs account ID), or any constraints. This leaves the agent without meaningful parameter semantics beyond the schema's bare type declarations.

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 uses a specific verb 'assign' with a clear resource ('issue') and recipient ('user'), which precisely identifies the tool's function. It also distinguishes this tool from sibling tools like jira_transition_issue (status change) and jira_add_comment, which handle different operations.

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?

No guidance is provided on when to use this tool versus alternatives. While the verb 'assign' implies its purpose, there is no explicit statement about appropriate contexts, prerequisites, or when to choose it over sibling tools.

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