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 tool ('Create'), implying it's a write/mutation operation, but doesn't disclose behavioral traits like required permissions, rate limits, error handling for partial failures, or whether it's idempotent. For a batch write 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 with zero waste. It's front-loaded with the core action ('Create multiple CRM objects') and adds necessary context ('in a single request'). Every word earns its place.

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?

Given the complexity (batch write operation with 2 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain parameters, behavioral constraints, or output format. For a tool that creates multiple objects with nested structures, more guidance is needed.

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. It mentions 'CRM objects' and 'single request', but doesn't explain the two parameters ('objectType' and 'inputs') or their structure. The description adds minimal value beyond what's inferred from the name, failing to clarify parameter meanings or usage.

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'), specifying it's a batch operation ('in a single request'). It distinguishes from single-object creation tools like 'crm_create_object' by emphasizing 'multiple' and 'batch', but doesn't explicitly contrast with other batch 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 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', 'crm_batch_create_contacts'), the description doesn't explain when this generic batch tool is preferable over type-specific ones or single-object creation.

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