clio_list_communications

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

The description mentions routing through a specific endpoint with JWT/tenant/company scope, offering minimal context. However, it does not disclose behavioral traits such as return format, pagination, rate limits, or any side effects. With no annotations, this is insufficient.

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 and contains no redundant phrasing, but the routing information adds bulk without aiding invocation. The structure is acceptable but not well-organized for quick scanning.

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?

Even with an output schema present, the description omits essential context about what communications are, whether filtering is possible, and what the response contains. This incompleteness hinders proper invocation.

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 single parameter 'arguments' is described as a JSON string for the connector operation, which adds minimal meaning beyond the schema. With 0% schema description coverage, the description fails to explain expected keys or structure, leaving the agent to guess.

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 identifies the tool as a connector operation to list communications, providing a clear verb and resource. However, it does not specify what constitutes 'communications' (e.g., emails, messages, notes), nor does it distinguish from sibling list tools like clio_list_activities or clio_list_bills.

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. The description does not mention prerequisites, typical use cases, or comparison with other Clio list tools, leaving the agent without decision support.

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