get_time_entries

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

No annotations are present, so the description carries the full burden. It mentions the source (Clio) and billable hours, but does not disclose pagination, default filter behavior, or authentication requirements. The read-only nature is implied by 'Get' but not explicit.

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 two sentences with no fluff. The first sentence states the core action, and the second gives a usage context. Every word earns its place.

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 a simple getter with 3 optional parameters, the description is adequate but not thorough. It doesn't explain what happens when no filters are provided, or mention any limitations. The output schema covers return values, but behavioral gaps remain.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description's mention of 'case' aligns with matter_id, but 'attorney' is not a filterable parameter, which could slightly confuse. No additional parameter detail is added beyond the 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 description clearly states 'Get time entries (billable hours) from Clio' – a specific verb and resource. It also distinguishes from sibling tools like get_matter_tasks by emphasizing 'review time spent on a case or by an attorney.'

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 sentence 'Use this to review time spent on a case or by an attorney' provides a direct usage context. It doesn't explicitly mention alternatives or exclusions, but the guidance is clear and sufficient for basic selection.

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