clio_create_matter

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

Annotations already signal a write operation (readOnlyHint=false) and destructive behavior (destructiveHint=true). The description adds useful context beyond the annotations by revealing an approval-gated write workflow: effect is a 'claimed read or write effect; Spring verifies it' and approval_ref is needed 'when resuming a write.' However, it never explains why a create is flagged destructive, and the approval prerequisites are left implicit.

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 purpose is front-loaded in a single sentence and the Args list is compact with no filler prose. However, the blank 'description' entry is dead weight, 'practice_area_id: Practice area ID.' is a tautology, and the misleading 'required' flags add noise that a leaner list would omit.

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 10-parameter tool with zero schema coverage and three overlapping correlation identifiers (project_id, project_ref, connector_account_ref), the description leaves an agent unable to determine which identifier to supply in which scenario. The non-obvious approval flow (effect + approval_ref) is never tied to the sibling approval tools (list_pending_approvals, approve_task, reject_task) that would explain when resuming a write is necessary. The output schema covers return values, but the input-side ambiguity is significant.

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?

With 0% schema description coverage, the description bears the full burden and partially delivers: client_id, project_id, connector_account_ref, idempotency_key, effect, and approval_ref all gain real meaning. But the 'description' entry is an empty line, practice_area_id merely restates its name, and project_ref ('Exact project correlation reference') remains vague. The 'required' markers that contradict the schema's zero required params actively mislead rather than clarify.

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 opening sentence 'Create a new Clio matter.' states a specific verb and resource, distinguishing it from sibling create_* tools (clio_create_contact, clio_create_bill, clio_create_task) and matter read tools (clio_get_matter, clio_list_matters). Minor deduction: three parameters are marked 'required' in the description while the schema declares zero required, which slightly muddies the declaration.

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 given about when to use this tool versus clio_update_matter, clio_get_matter, or clio_api_request, nor about prerequisites such as first resolving client_id via clio_list_contacts or clio_create_contact. The description is purely a parameter list with zero invocation-scenario context.

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