jira_get_sprint_issues

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It does not mention that this is a read-only operation, pagination behavior (though parameters exist), error cases, or what the return format is. Minimal transparency.

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 efficiently conveys the core purpose. While it could include more detail without becoming verbose, the current length is not wasteful. It earns a 4 for being succinct.

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 has 4 parameters, no output schema, and no annotations, the description lacks completeness. It does not explain what 'all issues' means in terms of response structure, pagination defaults, or how JQL interacts with sprint membership. Agent needs more context.

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% (all parameters have descriptions), so baseline is 3. The description adds no extra meaning beyond the schema; it simply says 'all issues' without clarifying that parameters like jql, startAt, and maxResults can be used to filter and paginate.

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 retrieves all issues in a specific sprint, using a specific verb and resource. It distinguishes from siblings like jira_search_issues and jira_get_board_issues by specifying the sprint context.

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 provides no guidance on when to use this tool versus alternatives like jira_search_issues (which can filter by sprint via JQL) or jira_get_board_issues. No when/to use or when-not-to-use information is given.

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