Get Backlog

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

With no annotations, the description carries the transparency burden. The phrase 'not assigned to any active sprint' clearly discloses the selection logic. The 'List' verb implies a read-only operation, though it is not explicitly stated. The presence of an output schema covers return format details.

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 a single concise sentence that immediately conveys the tool's purpose and scope, with no filler or redundancy.

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 tool's simplicity, an output schema is present, and the description explains the core selection criteria, the contextual coverage is sufficient. Slight ambiguity about what constitutes an 'active sprint' exists, but it is not a significant gap for a list operation.

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 input schema already provides full descriptions for both optional parameters (status and priority). The tool description adds no additional parameter semantics, so the baseline score of 3 applies for high schema coverage.

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 clearly states the tool lists issues not assigned to any active sprint, using a specific verb and resource. This distinguishes it from sibling tools like listIssues and listSprints, making the purpose unambiguous.

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?

The description implies when to use this tool (when you need backlog items) and defines the exact scope, which differentiates it from generic issue lists. However, it does not explicitly mention alternatives or exclusions such as using listIssues for all issues.

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