Matters with unbilled time

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

With no annotations, the description must carry the behavioral burden; the verb 'Lists' implies a read-only retrieval, and it discloses the filtered dataset (unbilled time). It says nothing about pagination behavior, ordering, result size, or rate limits for an 8-parameter list endpoint.

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 compact sentences, front-loaded with the core behavior and the billing use case; no filler. It is efficient, though it could spend one more clause on the undocumented filters.

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?

For an 8-parameter list tool with no annotations and no output schema, the description is thin: it omits most filter parameters, says nothing about pagination or the shape of returned matter records, and gives no prerequisite/permission context.

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 8 parameters, so the description must compensate. It only accounts for the period (start_date/end_date) and client filters, leaving matter_id, responsible_attorney_id, query, limit, and page_token entirely undocumented anywhere.

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 and resource ('Lists matters with unbilled hours/amounts') plus the business purpose ('basis for preparing bills'), which meaningfully separates it from clio_bills_list and clio_matter_search. It does not, however, name any sibling or explicitly contrast its scope with them.

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?

'Intended for monthly billing' and the optional period/client scoping imply the usage context, but there is no explicit when-to-use vs. when-not guidance and no routing to alternatives like clio_bills_list or clio_outstanding_balances.

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