jira_get_sprint_issues

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

The description notes the tool is 'read-only', which is a key behavioral trait. However, with no annotations provided, it should disclose more (e.g., error conditions, rate limits). The brief statement partially compensates but is insufficient for full 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 very short and front-loaded with the core purpose. However, it omits critical details, so conciseness comes at the cost of completeness. Still, it earns points for efficiency.

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 presence of an output schema (not shown) and lack of annotations, the description is incomplete. It fails to explain parameter semantics, return format, or any edge cases, leaving significant gaps for an agent to fill.

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 0%, and the description does not explain the parameters (sprint_id, limit). The agent receives no guidance on parameter meaning or usage beyond the schema's technical definitions.

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 action ('List issues') and the resource ('in a sprint'), with a parenthetical '(read-only)' that adds clarity. It distinguishes this tool from siblings like 'jira_get_issue' (single issue) and 'jira_get_sprint' (sprint details).

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'jira_search' or 'jira_get_issue', nor does it mention prerequisites or limitations.

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