jira_move_issues_to_backlog

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

Annotations only declare readOnlyHint=false, confirming a mutation, which the description's 'Move' already implies. The description adds nothing beyond that: it does not say whether issues are removed from an active sprint, whether the move is reversible, what permissions are required, or what the response contains. For a mutation with minimal annotation coverage, this is a real gap.

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?

One short, front-loaded sentence with zero waste, so it is efficient. The terseness is a completeness problem rather than a conciseness one, so it stays near the top of the scale but is not exemplary.

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 mutating bulk operation with no output schema and only a readOnlyHint annotation, the description leaves out the side effects an agent needs (sprint removal, ordering impact) and any return information. It is under-specified relative to the tool's complexity.

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% and the single parameter ('issues', with format example and minItems) is fully documented in the schema. The description adds no additional semantics, so the baseline of 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?

The description gives a specific verb ('Move') and resource ('issues to the backlog'), so the agent knows exactly what operation is performed. It does not, however, distinguish this from related siblings such as jira_add_issues_to_sprint or jira_list_backlog, leaving the agent to infer the difference from the tool names alone.

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 when-to-use guidance, no mention of alternatives (e.g. adding to a sprint instead), and no prerequisites or context about when backlog is the right destination. The agent gets a bare operation with no routing help.

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