clio_list_time_entries

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

With no annotations, the description must convey behavioral traits. It only mentions routing information (JWT, tenant, scope) but does not disclose whether the operation is read-only, safe, or has rate limits or pagination behavior. The description adds minimal transparency beyond technical routing.

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?

The description is short but wasteful—it includes overly technical routing details that do not aid an AI agent in selecting or invoking the tool. It lacks a clear, front-loaded purpose statement and uses space on infrastructure concerns rather than functional guidance.

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?

Considering the lack of annotations, zero schema description coverage, and the presence of an output schema, the description should compensate but does not. It omits essential context like return value structure, pagination, or filtering capabilities, making it insufficient for an agent to use correctly.

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?

The sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation.' Given 0% schema description coverage, the description fails to clarify what keys or values are expected in that JSON. It adds no meaningful semantics beyond the parameter name.

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 merely states 'Clio connector operation list_time_entries' which restates the name without explaining what listing time entries entails. It does not distinguish this tool from sibling tools like clio_list_activities or clio_list_bills, leaving the agent unclear about the specific resource being listed.

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 provided on when to use this tool versus alternatives such as clio_create_time_entry or clio_search. There is no mention of prerequisites, context, or exclusion criteria, leaving the agent without direction on appropriate invocation.

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