jira_rank_backlog

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds some useful context beyond annotations: the governed-authority routing constraint, the idempotency_key purpose, that 'effect' is verified by Spring, and that approval_ref is needed when resuming a write. However, it never discloses what the rank operation actually changes on the Jira side or the consequences of the destructive hint. No contradiction with annotations.

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 docstring is well-structured with a flat Args list, no filler prose, and the identity and governance constraint are front-loaded. The only redundancy is the parenthetical platform path '(platform tool jira.rank_backlog)', which adds minimal value beyond the first clause. Overall, appropriately sized and scannable.

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?

An output schema exists, so return values need not be explained, and every parameter gets at least a label. However, the tool's core domain behavior is undefined, the JSON 'arguments' payload is a black box, and the governance workflow (how project_id, project_ref, and connector_account_ref relate, and how approval_ref is obtained for writes) is only hinted at. For a tool with this much routing and approval machinery, an agent cannot confidently construct a correct call.

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?

With 0% schema description coverage, the description carries the full documentation burden and does provide a one-line gloss for all 7 parameters, which is meaningful compensation. But several glosses are near-tautological ('project_ref: Exact project correlation reference'), and the most important parameter, 'arguments' (the JSON string payload for the connector operation), is left completely opaque—the description never says what a rank_backlog arguments payload should contain. Partial but incomplete compensation.

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 only restates the operation identity ('Jira connector operation rank_backlog (platform tool jira.rank_backlog)') without explaining what ranking a backlog does—e.g., reordering issues by priority. The verb 'rank' plus resource 'backlog' is named, but the domain semantics are never defined, so the description borders on tautology and does not distinguish from similar-sounding siblings like coding_prioritize_backlog.

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 select this tool versus alternatives, no exclusions, and no mention of any sibling tool. The only contextual sentence, 'Routes only through the exact project/account governed connector authority,' describes an operational routing constraint, not a selection condition. An agent is given no basis for deciding this tool is the right one.

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