crm_batch_create_objects

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

No annotations are provided, so the description carries full burden. It states this is a creation operation but doesn't disclose any behavioral traits: no information about permissions required, whether it's idempotent, rate limits, error handling for partial failures, or what happens when associations fail. For a batch mutation tool with zero annotation coverage, this is inadequate.

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 states the core functionality without unnecessary words. It's appropriately sized and front-loaded with the essential information about batch creation.

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 (associations, properties), no annotations, and no output schema, the description is insufficient. It doesn't explain what constitutes a valid CRM object, how associations work, what properties are expected, or what the tool returns. The combination of complexity and lack of structured documentation requires more descriptive content.

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%, meaning parameters are completely undocumented in the schema. The description adds no information about what 'inputs' or 'objectType' mean, their formats, or constraints. With 2 parameters (including a complex nested 'inputs' array), the description fails to compensate for the schema's lack of documentation.

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 CRM objects') and scope ('in a single request'), which is a specific verb+resource combination. It distinguishes from single-object creation tools like 'crm_create_object' by emphasizing batch capability, though it doesn't explicitly differentiate from other batch creation tools like 'crm_batch_create_companies' or 'crm_batch_create_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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, limitations, or when to choose batch creation over individual creation tools. With many sibling tools available (including other batch creation tools for specific object types), this lack of guidance is a significant gap.

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