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 offers minimal behavioral insight. It mentions batch creation but doesn't disclose critical traits like whether this is an atomic operation, error handling for partial failures, rate limits, authentication requirements, or what happens on success/failure. For a mutation tool with complex inputs, 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 communicates the core functionality without waste. It's appropriately sized for the tool's purpose and gets straight to the point.

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 no annotations, 0% schema description coverage, no output schema, and complex nested parameters, the description is insufficient. It doesn't address behavioral expectations, parameter meanings, error handling, or differentiation from sibling tools, leaving significant gaps for an AI agent to understand proper usage.

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%, but the description adds no parameter information beyond what's implied by the tool name. It doesn't explain the 'objectType' enum values or the structure of 'inputs' array elements. With 2 parameters (one with enum) and complex nested schemas, the description fails to compensate for the schema's lack of descriptions.

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 verb ('Create') and resource ('multiple CRM objects') with the operational context ('in a single request'). It distinguishes from single-object creation tools but 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. With many sibling tools including specific batch creation tools (e.g., crm_batch_create_companies) and a generic single-object creation tool (crm_create_object), the description offers no context for choosing this multi-object, multi-type batch tool over more specialized options.

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