crm_batch_create_contacts

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

No annotations are provided, so the description carries full burden. While 'create' implies a write operation, the description doesn't disclose critical behavioral traits: whether this requires specific permissions, rate limits, whether contacts are created synchronously or asynchronously, error handling for partial failures, or what the response contains. For a batch mutation tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for conveying the core functionality without unnecessary elaboration.

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 batch creation tool with complex nested parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the parameter structure, expected response format, error handling, or operational constraints. The agent would struggle to use this tool correctly without additional documentation.

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%, and the description provides no parameter information beyond implying an array input. The complex nested schema with 17+ property fields and association objects is completely undocumented in the description. With low schema coverage, the description fails to compensate by explaining parameter meanings, formats, or requirements.

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 'Create multiple contacts in a single request' clearly states the verb ('create') and resource ('contacts'), with the 'multiple...in a single request' indicating batch functionality. It distinguishes from non-batch contact creation tools like 'crm_create_contact', but doesn't explicitly differentiate from other batch creation tools like 'crm_batch_create_companies' or 'crm_batch_create_leads'.

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. The description doesn't mention prerequisites, limitations, or when batch creation is preferred over single-contact creation. With many sibling tools available, the agent receives no help in selecting this specific batch contact creation tool.

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