create_matter

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

No annotations provided. The description indicates it creates a matter (mutation) but does not disclose potential side effects, permissions required, or error conditions. Minimal behavioral information beyond the fact of creation.

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 brief (two sentences plus a bullet list) and front-loads the core purpose. No unnecessary words, but could be slightly more structured.

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?

Covers the required parameters but omits explanation of optional parameters (status, description). No mention of return values (output schema exists but not referenced). Lacks context on validation, error handling, or usage constraints for a creation tool.

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 explains matter_type_id as from list_matter_types, client_ids_csv as comma-separated contact IDs, and number as optional. However, it does not explain the status, description, or any other optional parameters. Coverage is partial but adds meaning beyond the bare 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 matter and specifies required parameters (matter_type_id and client_ids_csv). It does not explicitly distinguish from sibling tools like add_file_to_matter or archive_matter, but the purpose is evident from the name and description.

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 (e.g., update_matter, create_lead). It mentions required parameters and that matter_type_id comes from list_matter_types, but does not specify prerequisites or constraints.

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