Create matter

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

The description discloses the flat_rate quirk (the two-step process and ignored billing_method), which is beyond annotations. However, it omits other behavioral details like auth needs, idempotency (annotations false but not elaborated), and side effects.

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 very concise (two sentences) with front-loaded purpose. Every word adds value, especially the critical flat-rate detail. No wasted text.

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?

Given the tool's complexity (11 parameters, creation, no output schema), the description covers the core purpose and one quirk but lacks error handling, return value hints, and differentiation from similar creation tools. It leaves gaps.

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 64%, and the description adds meaningful detail for flat_rate_amount by explaining the PATCH behavior. For other parameters, it restates schema info or adds nothing new. Overall, adds moderate value beyond the schema.

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 it creates a new matter and specifies the required client_id. However, it does not differentiate from the sibling tool clio_open_new_matter, leaving ambiguity about which to use.

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 creating matters but provides no guidance on when to use this tool versus alternatives like clio_open_new_matter, nor does it specify prerequisites or context.

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