clio_create_contact

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

With no annotations provided, the description carries the full burden. It discloses the two creation modes and their parameter mapping, but does not mention side effects, required permissions, or error behavior. This is minimally adequate but lacks depth for a mutation tool.

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?

One sentence, front-loaded with the action, then concise parameter guidance. Every word earns its place with no filler.

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 simple create tool with 4 parameters and no output schema, the description covers the core usage and type-specific fields. It lacks details on return values or prerequisites, but the essential behavior is clear enough for an agent to invoke it correctly.

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 description coverage is 0%, so the description must compensate. It effectively maps 'type' to Person/Company and explains when to use first/last_name versus name, adding meaning beyond the raw schema. It does not describe each parameter individually but provides the essential usage pattern.

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?

Description starts with 'Create' which is a specific verb for a write operation, and identifies the resource as 'client or party'. This clearly distinguishes it from sibling read tools like clio_find_contacts and clio_get_contact.

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?

Explicitly instructs on how to use the tool for two entity types: 'type=Person with first/last name, or type=Company with name'. This provides clear context on which parameters to use in which scenario, though it does not explicitly name alternative tools for reading contacts.

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