Get sprint issues

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully discloses that Cloud and Data Center use different API endpoints and paging mechanisms, which is valuable behavioral context. However, it does not mention return format, pagination loop behavior, authentication requirements, or rate limits, so there are still notable gaps.

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 primary purpose is front-loaded, and the Cloud versus Data Center distinction is stated compactly. Every sentence contributes meaningful information.

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?

The description covers the core purpose and the main environment-specific behavioral difference, which is good for a list tool. However, there is no output schema and no annotations, so the description could have usefully noted what the response contains, how fields controls the returned attributes, or how to page through all results. These omissions leave the definition adequate but incomplete.

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 80%, so the parameter descriptions already document most semantics, including that startAt is Data Center only and nextPageToken is Cloud only. The tool description adds context about 'enhanced endpoint with cursor paging' versus 'Agile 1.0 with startAt/total,' but this largely reinforces what the schema already says rather than adding significant new parameter meaning.

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 opens with 'List the issues in a sprint,' a specific verb and resource that makes the tool's purpose immediately clear. It also distinguishes itself from siblings like get_sprint (which returns sprint metadata) and get_epic_issues by focusing on sprint-scoped issues, and adds Cloud/Data Center endpoint 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 clearly states the tool is for listing issues in a sprint and gives environment-specific guidance: Cloud uses cursor paging while Data Center uses startAt/total. It does not explicitly name alternatives or state when not to use it, so it falls short of a 5, but the intended use context is unambiguous.

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