jira_assign_issue

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

Annotations already mark the tool as mutating and destructive, and the description adds useful context beyond that: it names the governed routing constraint, explains that 'effect' is verified by Spring, mentions idempotency_key as a stable business-action identity, and states approval_ref is for resuming a write. This is consistent with the annotations, so no contradiction.

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 compact and front-loaded: one routing sentence followed by a concise parameter list. It wastes little space, though the opening line is somewhat redundant with the tool name and the parameter descriptions are terse to the point of jargon.

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?

While an output schema exists and annotations cover safety, the description never explains what assign_issue actually does in Jira or how to construct the 'arguments' JSON (e.g., issue key, assignee). Combined with the absence of sibling guidance and all-optional parameters, an agent would struggle to invoke this correctly despite the provided platform-level context.

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 0%, so the description must compensate, and it does with a per-parameter Args list that clarifies project_id, project_ref, connector_account_ref, idempotency_key, effect, and approval_ref. The 'arguments' parameter is only described as a generic JSON string, which leaves the domain payload unexplained, but the added parameter semantics are still substantial.

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 identifies the resource and operation ('Jira connector operation assign_issue', platform tool jira.assign_issue), and the verb 'assign' is reasonably self-explanatory in a Jira context. However, it does not explain the actual assignment semantics (e.g., assigning to a user) or differentiate from nearby siblings like jira_update_issue or jira_transition_issue beyond the name.

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?

There is no guidance on when to choose assign_issue over alternatives such as jira_update_issue or jira_transition_issue. The routing constraint 'Routes only through the exact project/account governed connector authority' describes a precondition, not usage context, and no when-not-to-use conditions are given.

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