jira_get_sprint_issues

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), lowering the bar. The description adds some valuable context beyond annotations: the governed-connector routing constraint and the fact that Spring verifies the read effect. However, the approval_ref gloss ('Approved platform task UUID when resuming a write') is misleading boilerplate on a read-only tool, and there is no mention of pagination or return behavior. No direct contradiction with annotations.

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 structure is clean and scannable: a two-line header followed by a labeled Args list, with the key routing constraint front-loaded. But not every sentence earns its place — the opening line duplicates the tool name, and the approval_ref line is write-resume boilerplate that is irrelevant and potentially confusing for a read-only tool.

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?

With an output schema present and rich annotations, the description need not explain return values or safety. The remaining critical gap is operational: it never says what the Jira operation actually needs inside the `arguments` JSON (e.g., a sprint ID or board ID), leaving the agent unable to construct a correct call from the description alone. The routing and effect semantics are covered, but the core invocation payload is not.

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%, so the description carries the full burden, and it compensates by glossing all 7 parameters (arguments as a JSON string, project_id as an Authenticated Project UUID, connector_account_ref as a project-bound alias, etc.). These role labels add meaning beyond the bare schema titles and defaults, though several are terse and generic — 'exact project correlation reference' and 'stable business-action identity' leave the actual value format unspecified.

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 by restating the tool name verbatim ('Jira connector operation `get_sprint_issues` (platform tool `jira.get_sprint_issues`)') and never explains what the operation actually does — i.e., retrieve the issues belonging to a Jira sprint. The remaining content covers routing and argument roles, not function. No behavioral differentiation from siblings like jira_get_issue, jira_get_board_sprints, or jira_search_issues.

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 guidance is given on when to use this tool versus alternatives. The routing statement ('Routes only through the exact project/account governed connector authority') is a governance constraint, not a usage condition. There are no exclusions, no named alternatives, and no context indicating when get_sprint_issues is preferred over jira_search_issues or jira_get_board_sprints.

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