jira_rank_backlog

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

No annotations exist, so the description carries full burden. It mentions routing and JWT scope, but does not disclose whether the operation is destructive, idempotent, or requires specific permissions. The behavioral impact of 'rank_backlog' is not explained.

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 extremely short (two sentences). While concise, it lacks essential information, making it under-specified rather than efficiently informative.

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?

Given the simplicity of the tool (one parameter, output schema exists), the description should still explain the purpose and usage of 'rank_backlog' more fully. It fails to provide a complete picture, especially regarding return values or error conditions.

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 described simply as a JSON string. With 0% schema coverage, the description should clarify expected keys or structure, but it does not, leaving the agent uninformed about how to construct valid input.

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 tool as a Jira connector operation for 'rank_backlog', which implies reordering the backlog, but does not explicitly state the verb and resource with sufficient clarity. The name itself is descriptive, but the description adds little beyond that.

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 use this tool versus alternative Jira tools (e.g., jira_bulk_transition, jira_update_issue). No context is provided about prerequisites or typical scenarios.

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