jira_get_sprint_issues

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

No annotations are present, so the description carries the full burden. It mentions routing and JWT scope but does not disclose key behaviors like return format, pagination, or required permissions. The description adds minimal behavioral context beyond what is obvious from the tool name.

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 short but wasteful, repeating the tool name and including generic routing info that doesn't aid invocation. The structure is standard but content is insufficient, making it under-specified rather than concise.

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 no annotations, no parameter descriptions, and a sparse description, the tool is incomplete. The agent cannot determine how to correctly invoke it (e.g., required JSON keys) from the provided text alone.

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 only parameter 'arguments' is described as 'JSON string of arguments for the connector operation' without any detail on expected keys or structure. Schema coverage is 0%, so the description must compensate, but it fails to explain what should be included in the arguments JSON.

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 merely restates the tool name ('Jira connector operation get_sprint_issues') without explaining what the tool does. It does not specify that it retrieves issues for a specific sprint, leaving the agent to infer purpose from the name alone, which is insufficient.

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 provided on when to use this tool versus sibling tools like jira_search_issues or jira_get_board_sprints. There are no prerequisites or context for usage, such as the need for a sprint ID or board ID.

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