clio_find_communications

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the basic function and filters, but does not mention whether the operation is read-only, any required permissions, pagination behavior, or the structure of the response. This is a significant gap for a list tool.

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 sentence, front-loaded with the verb 'List', and contains no redundant information. It is appropriately concise for the tool's purpose.

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 tool has no output schema, no annotations, and a 0% schema description coverage. The description does not explain the return format, pagination limits beyond the schema, or any operational caveats. It is insufficient for an agent to fully understand the tool's behavior in 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?

The description adds meaning to some parameters by mentioning 'matter, contact, or date range', which maps to matter_id, contact_id, and to/from. However, it does not explain the exact nature of to/from (likely dates) or provide details for limit. Since the schema has no property descriptions, this partial compensation earns a midpoint score.

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 verb 'List' and the resource 'logged communications', and specifies filters (matter, contact, date range). This distinguishes it from sibling tools like clio_get_communication (single item retrieval) and clio_log_communication (creation).

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 using this tool when a list of communications is needed with filtering options. However, it does not explicitly mention when to use alternatives like clio_get_communication for individual communications, nor does it provide exclusions or prerequisites.

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