clio_list_matters

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention read-only nature, pagination, ordering, rate limits, or any side effects. For a list tool, such omissions are significant.

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?

Extremely concise: one-line purpose plus two parameter explanations. No redundant information. Well-structured with clear 'Args' section. Every sentence 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?

Output schema exists, so return values are covered elsewhere. However, missing pagination, sorting, or limit information that is typical for list tools. The description is functional but leaves gaps for complex use cases.

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?

Schema coverage is 0%, so description must add meaning. It explains 'status: One of: pending, open, closed.' (even though schema lacks enum) and 'client_id: Filter to a specific Clio contact ID.' These add value beyond the bare JSON schema. Could be more detailed (e.g., format requirements).

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 'List Clio matters for the connected firm.' This is a specific verb (list) and resource (matters). Among many clio_list_* siblings, it unambiguously identifies the tool's function. However, it does not differentiate beyond the resource name.

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 on when to use this tool versus alternatives like clio_get_matter or clio_search. The description only lists parameters without context on when filtering is appropriate. No exclusions or alternative suggestions.

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