jira_get_backlog_stats

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

Discloses default grouping, custom pivoting, and aggregation actions. However, it claims 'any field pair' pivoting, which the schema's enum lists contradict—behavioral overstatement. With no annotations, the description carries burden but is partially misleading.

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?

One dense sentence that front-loads the core function and key capabilities without wasted words. Efficient and well-structured.

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 tool with 9 parameters, nested pivot object, and no output schema, the description gives a good overview but omits several filter parameters (sprint, boardId, assignees, etc.). The overstatement reduces reliability, though schema fills most gaps.

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 covers 100% of parameters with descriptions, so baseline applies. The description adds context for pivot and fieldFilters, but the 'any field pair' claim is inaccurate given the schema enums, so it adds no real value beyond the schema.

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 states it 'gets aggregated statistics for issues matching a JQL query' and lists default groupings, clearly distinguishing it from raw issue retrieval tools like jira_search_issues. Specific verb and resource make it unambiguous.

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 implies use for statistical aggregation via 'aggregated statistics' and mentions pivoting/filtering, but it does not explicitly contrast with alternative tools or state when not to use it. Clear context, but no exclusions.

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