Case processing duration

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

No annotations are provided, so the description carries the burden; it does clarify that results are aggregated (one row per group) and lists the returned metrics. It does not mention read-only nature, default time window, permission needs, or ordering/pagination of groups.

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?

Two sentences, front-loaded with the metric definition and followed by the output shape; nothing is wasted.

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 output schema covers return values, and the description correctly explains the metric. But with six parameters at 0% documentation, an agent still cannot tell how to format or scope the timestamp filters or what group_by accepts.

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 coverage is 0%, so the description must compensate for 6 undocumented parameters. It only hints at three group_by dimensions (priority, issue_type, report_channel) and ignores timestamp_from, timestamp_to entirely, giving no format or filtering semantics.

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?

States a specific verb+resource ('Aggregate case processing duration') plus the exact metric definition (first event to last event) and the grouping dimensions. An agent can tell what it computes, though the siblings listed are unrelated operations so no differentiation is offered.

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?

There is no indication of when to use this versus alternatives, no prerequisites, and no note about whether filters are combinable or whether group_by is mandatory. Usage is only implied by the tool name.

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