Create multiple activities/interactions in one call. Max 50 items per batch. Runs atomically - if any item fails, the entire batch is rolled back.
| Name | Required | Description | Default |
|---|---|---|---|
| activities | Yes | Array of activity creation inputs (max 50) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It prominently discloses atomicity and rollback semantics, a critical behavior for a batch operation. It also states the batch size limit. Although it does not cover response format or permissions, the most important behavioral trait is covered.
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 two sentences, front-loaded with the core action and followed by essential constraints. Every clause adds value: batch creation, size limit, and atomicity. There is no filler or redundant phrasing.
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?
The description covers the key contextual aspects of a batch create tool: batch size and atomicity. Since there is no output schema, the lack of return value documentation is acceptable. The description is sufficient for an agent to understand the tool's scope and major behaviors, though it could mention validation or error handling.
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 100%, with all parameters already explained in the schema. The description only repeats the max 50 items constraint, which is also present in the schema. Thus the description adds no significant parameter-level meaning beyond what the schema already provides.
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 primary action ('Create') and resource ('multiple activities/interactions') with the batch context ('in one call'). It distinguishes from sibling tools like activity_list or activity_manage by emphasizing batch creation, and the name itself is informative.
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 implicitly guides usage: use this when creating multiple activities at once. It provides concrete boundaries (max 50 items, atomic rollback) that help decide if this tool fits. However, it does not explicitly name alternative tools or state when not to use it, so it misses the 'when-not' aspect.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct by entity, but contact_get and contact_timeline overlap significantly, and debt_manage's action='list' duplicates what other entities do with a dedicated list tool. Descriptions are detailed enough to resolve most ambiguity, though.
Tool names are mostly snake_case and readable, but they mix conventions: noun_verb (contact_create), verb_noun (batch_create_activities), and descriptive phrases (contacts_needing_attention). The noun_manage pattern is dominant, but the lack of uniformity makes the naming less predictable.
With 42 tools, the surface is very large, even for a full-featured CRM. Many tools bundle multiple actions, but the sheer number forces an agent to consider many options, increasing selection difficulty and cognitive load.
The server provides comprehensive CRM coverage: contacts, activities, notes, tasks, reminders, gifts, debts, relationships, tags, custom fields, notifications, settings, and exports. It supports batch operations, duplicate detection, merge, and special queries, leaving few if any obvious gaps.