clio_create_matter

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

No annotations are present, so the description should disclose behavioral traits. It only states the basic creation action without mentioning side effects, permissions, error handling, or idempotency. The tool name implies mutation (create), which is expected, but no additional context is given.

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, fitting in a few lines. However, the argument list contains an empty description for the 'description' parameter, which wastes space. The structure (Args list) is straightforward but could be more informative.

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 (4 parameters, no annotations, output schema present), the description is incomplete. It fails to explain optional/required nature correctly, omits return value details, and lacks examples or validation rules. The output schema exists but the description does not reference it.

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 description lists parameters with brief descriptions (e.g., 'Clio contact ID for the client'), providing some semantics. However, it incorrectly marks three parameters as required when the schema indicates none are required, and the 'description' parameter has an empty description. Schema coverage is 0%, so the description partially compensates but with errors.

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 states 'Create a new Clio matter,' which clearly identifies the action and resource. It distinguishes from sibling update tools like clio_update_matter, but lacks explicit differentiation from other create tools such as clio_create_contact or clio_create_folder.

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 (e.g., clio_create_contact for creating a client contact). There are no prerequisites or context about typical usage scenarios.

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