Practice areas and matter stages

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

No annotations are provided, so the description carries the burden, but 'Lists' communicates a read-only retrieval. Beyond that it says nothing about pagination, caching, or whether results are tenant-scoped, though for a zero-argument enumeration call the behavioral surface is small.

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?

A single front-loaded sentence with no filler; the resource is named before the qualifier. It is efficient, though extremely terse relative to other Clio definitions.

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 no-parameter list tool with no output schema, the description covers what is returned but not how the two collections (practice areas vs. matter stages) are shaped or related in the response. No output schema exists to fill that gap, so a small ambiguity remains.

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 tool takes no parameters, so there is nothing for the description to clarify; the baseline for zero-param tools is 4. The description correctly does not invent any input semantics.

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?

States a specific verb (Lists) and the two resources returned (practice areas and matter stages), which is unambiguous. It does not explicitly contrast itself with any sibling, but the resource is distinctive enough that confusion is unlikely.

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 parenthetical '(for creating/updating matters)' implies the downstream use case, so an agent can infer this is reference data to fetch before clio_matter_create or clio_matter_update. There is no explicit when-to-use/when-not statement or named alternative, so the guidance stays at an implied level.

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