jira_get_sprint_issues

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

readOnlyHint=true already tells the agent this is a safe read, so the description is not required to restate safety. But it adds nothing beyond that: no note on pagination behavior despite a maxResults parameter, no scoping semantics, no indication that jql can further narrow the sprint results. The description carries no behavioral value the annotations don't.

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?

A single short sentence with no padding and the resource front-loaded. It is efficient, though the extreme brevity leans toward under-specification rather than disciplined conciseness.

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 described, but for a tool sitting among many overlapping issue-listing siblings the description is too thin. It omits how this differs from jira_get_board_issues/jira_search_issues and says nothing about the jql narrowing option or paging, leaving real gaps.

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% – sprintId, jql, and maxResults are all documented in the schema, including the pointer to jira_list_sprints. The description adds no parameter meaning on top of that, so the baseline of 3 applies.

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 states a clear verb+resource ('List the issues in a sprint'), so the basic purpose is legible. However, it does nothing to separate this tool from siblings like jira_get_board_issues, jira_list_backlog, or jira_search_issues, all of which also enumerate issues. Without that differentiation the agent must infer which is appropriate.

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 when-to-use guidance, no condition that selects this over jira_search_issues or jira_get_board_issues, and no mention of prerequisites such as needing a sprintId obtained from jira_list_sprints. The agent gets no routing help at all.

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