crm_batch_create_objects

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

With no annotations provided, the description carries full burden but only states it's a creation operation. It doesn't disclose critical behavioral aspects: whether this requires specific permissions, rate limits, error handling for partial failures, what happens on duplicate data, or response format. 'Create' implies mutation but lacks safety/performance context.

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?

Extremely concise single sentence with zero waste. Every word earns its place: 'Create' (verb), 'multiple' (batch scope), 'CRM objects' (resource), 'in a single request' (operational context). Front-loaded and efficiently 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?

For a batch creation tool with 2 parameters (one complex array), 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the multi-object creation process, parameter requirements, error scenarios, or what constitutes valid CRM objects. The conciseness comes at the cost of completeness.

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 but adds no parameter information. It doesn't explain what 'objectType' enum values mean, the structure of 'inputs' array, or the purpose of 'properties' and 'associations' fields. The description fails to provide any semantic context beyond the tool name.

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 multiple') and resource ('CRM objects'), specifying it's a batch operation ('in a single request'). It distinguishes from single-create tools like crm_create_object, but doesn't explicitly differentiate from other batch create tools like crm_batch_create_companies.

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 like crm_batch_create_companies/contacts/leads or crm_create_object. The description implies batch creation but doesn't specify scenarios where batch creation is preferred over individual creation or when to use type-specific batch tools.

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