Assign Issue

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

Annotations only say `readOnlyHint: false`, which is consistent with the write operation. The description discloses additional behavior: it uses the dedicated PUT endpoint, explains the identifier resolution order (key lookup → email search → text search → assignable-user search), and warns about the unreliability of `update_issue`. This goes well beyond the annotation.

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 three short, focused paragraphs. The first sentence states the core purpose, the second explains the advantage over an alternative, and the third provides essential identifier details. There is no fluff, and the structure front-loads the most important information.

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 an existing output schema, the description covers the endpoint, the reliability rationale, accepted identifier forms, and resolution order. It also clarifies that an empty string or null unassigns, which is reflected in the schema but helps the agent understand usage. No critical context is missing.

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%, so the schema already documents both parameters. The description adds valuable semantic detail about the `assignee` parameter, specifying accepted identifier forms (login name, email, display name, JIRAUSER key) and the exact resolution order. It also references the JSON object format from `jira_search_assignable_users`, which is not fully detailed in 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?

The description opens with a specific verb+resource: 'Assign a Jira issue to a user using the dedicated assignment endpoint.' It explicitly distinguishes itself from the sibling `update_issue` tool by noting that setting assignee via `update_issue` is silently ignored in some configurations, making the purpose and unique value clear.

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 explicitly tells the agent when to use this tool over `update_issue`: 'This is more reliable than setting assignee via update_issue, which is silently ignored by some Jira configurations.' It also mentions accepted identifier forms and the resolution order, providing concrete guidance on how to supply the assignee parameter, including a hint that JSON object strings from `jira_search_assignable_users` are acceptable.

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