get_statistics

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

Annotations (readOnlyHint, destructiveHint) already convey that this is a safe read operation, but the description adds no behavioral context. It does not disclose pagination behavior via cursor_next, the effect of dry_run, result format, or any side effects. The 'Python SDK parity' phrase is unexplained and unhelpful.

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 extremely short, but brevity comes at the expense of substance. It is not a well-structured description; it is a bare URL and an unclear note. The phrase 'Python SDK parity' is cryptic and does not earn its place without further explanation.

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?

This tool has 5 parameters, 2 required, no output schema, and many sibling statistics tools. The description fails to explain what statistics are returned, how cursor_next pagination works, what dry_run does, or how this tool differs from get_issue_stat. The available structured data (schema/annotations) does not compensate for these missing behavioral and contextual details, making the description severely 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?

The input schema covers all 5 parameters with descriptions (limit, date_to, dry_run, date_from, cursor_next), so the schema carries the full burden. The description adds no additional parameter semantics or usage details beyond what the schema already provides, hence the baseline score of 3.

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 only provides the endpoint path 'GET /api/v2/issue/statistics' and a vague note about Python SDK parity. It does not explain what statistics are retrieved, for what entity, or what the data represents, making it difficult for an agent to know what this tool actually does. It also fails to differentiate from sibling tools like get_issue_stat or get_overview.

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 rather than alternatives. The description does not mention any use cases, prerequisites, or situations where a different statistics tool would be more appropriate. Given the large sibling list, this omission is critical.

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