list_time_reports

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that output includes totals per person, which is real behavioral information beyond the annotations, but it says nothing about pagination (the schema's limit=100 default) or how entry-level rows relate to the aggregates.

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 short line with no padding, and the resource statement is front-loaded ahead of the filter hint. The semicolon-joined fragments read as telegraphic notes rather than a structured sentence, which slightly hurts parseability but wastes nothing.

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 7 optional parameters, no required parameters, and no output schema, the description carries full burden for describing the return shape, yet it is ambiguous whether results are raw entries or aggregated totals (or both) and does not mention pagination. For an aggregation-style reporting tool this leaves meaningful 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 coverage is 71%, so most parameters are already documented, and the description's "person/date filters" maps loosely onto member, from, and to. It does not clarify the "without sub-issues" vs "all its issues" scoping difference between identifier and projectIdentifier, which is the main semantic risk in this 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 phrase "Logged time for an issue or project, totals per person" identifies the resource (time reports) and what it yields (per-person totals), which implicitly separates it from the write-oriented log_time sibling. It is specific but lacks an explicit verb and never names the alternative, so the distinction must be inferred.

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 when-to-use or when-not-to-use language and no named alternative; the closest thing to guidance is the bare filter hint "person/date filters." An agent must guess that this is the read/aggregate counterpart to log_time.

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