jira_assign_issue

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

No annotations are provided, and the description does not disclose behavioral traits like whether the tool is read-only or mutates state. The description focuses on routing and argument format, not on what happens when the tool is invoked.

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 under-specified and fails to concisely convey the tool's purpose. It includes irrelevant routing details that do not help the agent understand when or how to use the tool. The description should be replaced with a clear, front-loaded statement of functionality.

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?

Despite having an output schema (which is not referenced), the description is completely inadequate. It does not explain the tool's behavior, input requirements, or output, making it nearly impossible for an AI 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?

The only parameter 'arguments' is a JSON string with no schema description coverage (0%). The description does not explain what keys or values are expected inside this JSON, leaving the agent to guess the required structure for assigning an issue.

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 name 'jira_assign_issue' suggests assigning an issue, but the description only states it's a 'connector operation' and mentions routing details. It does not explicitly state what the tool does (e.g., assign a Jira issue to a user) or differentiate it from sibling tools like jira_create_issue or jira_update_issue.

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 such as jira_transition_issue or jira_update_issue. There is no mention of prerequisites, typical use cases, or situations to avoid.

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