clio_find_calendar_entries

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

With no annotations, the description carries the full transparency burden. The verb 'List' implies a read-only operation, and the filter criteria are disclosed. However, it does not mention pagination, the significance of the limit parameter, or the response format, which are important behavioral traits.

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 a single, front-loaded sentence that avoids redundancy. Every word contributes to the core purpose and filter capabilities.

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?

The description covers the basic list-with-filters functionality, but it does not address pagination/limit behavior, how to retrieve a single entry, or what the response contains. Given the lack of annotations and output schema, more contextual detail would be beneficial.

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 has only 40% description coverage. The description adds meaning by tying 'calendar', 'matter', and 'date range' to the corresponding parameters, but it does not mention the 'limit' parameter or clarify that all filters are optional. It partially compensates for the schema gaps.

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 the tool lists calendar entries and specifies the filter dimensions (calendar, matter, date range). This distinguishes it from siblings like clio_get_calendar_entry (singular retrieval) and clio_list_calendars (lists calendars, not entries).

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 description implies usage for listing/filtering calendar entries, but it does not explicitly mention when to use this tool versus alternatives such as clio_get_calendar_entry for a single entry. No exclusions or alternative tool names are provided.

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