Time summary per matter/period

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

With no annotations, the description carries the full burden. It usefully discloses that the tool walks all pages and caps at 2000 entries (a truncation limit) and that output is broken down by user and billing status. It does not state read-only safety, required permissions, or pagination beyond the cap.

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 tight sentences, front-loaded with the aggregation and grouping, followed by the pagination caveat. No wasted words.

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 no annotations, no output schema, and 5 undocumented parameters, the description leaves important gaps: whether status filters or groups, the date format/default range, permission requirements, and the shape of the returned breakdown. It is not complete enough for confident 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?

Schema description coverage is 0% across 5 params, so the description must compensate. 'By matter, user and period' loosely maps to matter_id, user_id, and start/end_date, but the status enum is left ambiguous — 'billing status' reads as a group-by while the schema suggests a filter, and no date format or defaults are given.

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 (sums hours and amounts) and resource (time entries) plus the grouping dimensions (matter, user, period). This clearly distinguishes it from sibling list tools like clio_time_entries_list, though it never names an alternative explicitly.

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 aggregation framing implies 'use this for totals instead of listing entries,' but there is no explicit when-to-use guidance, no exclusions, and no mention of when a filtered list would be preferable. Usage is inferable rather than stated.

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