Assign issue

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, and the description is consistent with them. The description's extra content (unassign path) is already stated in the assignee parameter schema, so it adds little context on permissions, lookup failures, or what is returned.

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 short sentences, zero filler, with the primary action stated first and the unassign variant second. Every clause carries 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 simple 3-parameter mutation with no output schema, the description covers the action and both termination states, and annotations carry the safety profile. Minor gaps: user-resolution failure behavior and required permissions are not mentioned.

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 description coverage is 100%, so all three parameters are fully documented in the structured field, including 'site' and the exact-match-one-user constraint. The description only restates the assignee forms already in the schema, so baseline 3 applies.

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?

Specific verb+resource ("Assigns an issue to a user") with accepted identifier forms, and the inverse operation (unassign) stated. It does not acknowledge that jira_update_issue can also change an assignee, so sibling differentiation is incomplete, keeping it off a 5.

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?

Both modes of use are spelled out: supply an assignee string, or omit/null/'unassigned' to clear. There is no explicit statement of when to prefer this over jira_update_issue or a transition, and no prerequisites (resolve user first) are surfaced.

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