jira_list_sprint_issues

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint as true/false appropriately. The description adds no extra behavioral context such as pagination behavior, potential performance impact, or response format details, which are needed for a complete understanding.

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 with the verb and resource front-loaded. It is efficient, though it could be slightly longer to include basic usage guidance without becoming verbose.

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 low parameter coverage, missing usage guidelines, and no output schema context in the description, the tool is not fully documented. The annotations help but the description alone is insufficient for an agent to use the tool effectively in all contexts.

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% per context, and the tool description does not mention any parameters. While the schema itself provides minimal descriptions for sprint_id and response_format, the description adds no value to help the agent understand the meaning or usage of parameters like limit and offset.

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 verb 'list' and the resource 'issues in a given sprint'. It effectively distinguishes from sibling tools like jira_get_issue (single issue) and jira_search_issues (complex queries).

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. It lacks context on prerequisites (e.g., need a sprint_id) or when to prefer list vs search. No exclusions or usage hints are given.

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