Create contact

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

No annotations are provided, so the description carries the full burden. It discloses the write operation and the chaining behavior, but does not mention side effects, idempotency, return values, or error conditions. The prerequisite is useful but minimal 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?

Two sentences, 30 words, front-loaded with action and key behavior. No wasted words. Ideal for quick scanning.

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?

Despite moderate complexity (9 parameters, no output schema, no annotations), the description is minimal. It omits return value format (e.g., the created contact ID), error scenarios, and defaults. For a creation tool, the agent needs to know what happens on success and failure.

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 44%, meaning only 5 of 9 parameters have descriptions. The description adds context that email and phone are chained, which adds meaning beyond the schema. However, it does not explain 'extra' or provide guidance on required fields. At 44% coverage, the description should compensate more.

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 the action ('Create a new CiviCRM contact') and the resource, along with a key feature ('Chains email and phone creation when provided'). This distinguishes it from siblings like civicrm_update_contact or civicrm_find_contacts.

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 mentions a prerequisite ('Requires CIVICRM_ALLOW_WRITES=true') but does not provide guidance on when to use this tool versus alternatives, such as when to update vs create. Usage is implied but not explicit.

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