Get board backlog

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

With no annotations, the description carries the burden, and it discloses meaningful behavior: backlog definition, rank ordering, and Cloud vs Data Center differences with cursor paging versus startAt/total. It does not cover auth, rate limits, or response shape, but for a read-only list operation the key behavioral traits are present.

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?

Two dense sentences with no filler. The core definition and scope appear first, followed by relevant version-specific behavior. Every clause earns its place.

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?

The description, combined with a well-documented schema, covers what the tool does, its scope, ordering, and platform-specific pagination. The absence of an output schema means return format is not fully specified, but the description and field defaults provide reasonable context for an agent to invoke it 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?

Schema coverage is 83%, so the schema already documents most parameters. The description adds context about pagination modes matching Cloud vs Data Center, but it does not materially deepen the meaning of jql, fields, or boardId beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific action ('List'), a precise resource ('a board's backlog issues'), a scope definition ('in the board's filter, not in a sprint'), and an ordering ('by rank'). This clearly distinguishes it from sprint-issue tools and general search tools.

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?

Provides clear context about what constitutes a backlog and scopes it away from sprints, which implies when to use this over get_sprint_issues or search_issues. However, it does not explicitly name alternatives or state when not to use the tool.

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