kaiten_get_sd_stats

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

With no annotations, the description must carry the full behavioral disclosure burden, but it only states 'Get', implying a read operation. It does not disclose whether report mode triggers a heavier/compute operation, what the API returns, whether date filters are required, or any side effects.

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?

A single concise, front-loaded sentence contains no wasted words and is easy for an agent to scan. Its brevity is appropriate for a simple retrieval tool, though it sacrifices informative depth.

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 tool has no output schema and no annotations, yet the description provides no context about the returned statistics, the meaning of report mode, default date behavior, or how service_id influences results. For a statistics tool, this is insufficient context for reliable invocation.

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?

All four parameters have their own descriptions in the schema (100% coverage), so the schema already explains report, date_from, date_to, and service_id. The description adds no additional parameter semantics, but the high schema coverage meets the baseline.

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 names a concrete target ('Service Desk statistics') and a read verb, but leaves the scope and nature of the statistics undefined. It does not distinguish this from the closely related sibling kaiten_get_sd_sla_stats or the kaiten_chart_* statistics tools.

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 about when to choose this tool instead of alternatives. The description does not mention SLA-specific statistics, date-range filtering use cases, or when the report parameter should be enabled versus the other statistics/report tools.

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