get_my_current_sprint_issues

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

No annotations are provided, so the description carries the behavioral transparency burden. It does convey the read-only 'get all issues' behavior and the active-sprint scoping, which is useful. However, it does not disclose edge behaviors such as what happens when there are no active sprints, whether multiple active sprints are merged, or whether returned issues are limited to open/unresolved ones.

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 two sentences with no filler. The core purpose is front-loaded, followed by concrete example use cases and a brief note on filtering. Every sentence earns its place.

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?

For a simple read-only list tool with fully documented optional parameters and no output schema, the description provides enough context to call it correctly. It explains what the result is (issues assigned to the user in active sprints) and mentions the available filters. It could mention multi-board ambiguity or empty-sprint behavior, but those are minor gaps for this tool.

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 covers both parameters fully, so the baseline is 3. The description only says 'Can filter by specific board or project,' which adds no new semantic detail beyond the schema's property descriptions. It does not introduce additional format or behavior expectations for the parameters.

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 uses a specific verb and resource: 'Get all issues assigned to you in the currently active sprint(s).' This clearly distinguishes the tool from sibling tools like get_my_unresolved_issues or search_issues_by_user_involvement by focusing on active sprint scope. It is immediately obvious what the tool does.

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 gives clear usage context: 'Useful for daily standups or checking your current sprint workload.' It does not explicitly name when-not-to-use or compare to alternatives, but the use cases are specific and practical enough for an agent to recognize when this tool is appropriate.

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