crm_batch_create_leads

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but gives no information about permissions required, rate limits, whether the operation is idempotent, error handling for partial failures, or what the response contains. This is inadequate for a mutation tool with complex nested parameters.

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 no wasted words. It's appropriately sized for a tool name that already conveys the domain (CRM) and operation type (batch create).

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?

This is a complex mutation tool with no annotations, no output schema, and 0% schema description coverage for a deeply nested parameter structure. The description is completely inadequate - it doesn't explain what data leads require, how associations work, what happens on success/failure, or any behavioral constraints. The agent lacks critical information to use this tool correctly.

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 no parameters are documented in the schema. The description mentions 'multiple leads' but provides zero information about the required 'inputs' parameter structure, the nested properties object, or the associations array. The description fails to compensate for the complete lack of schema 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 leads') and resource ('leads'), making the purpose immediately understandable. However, it doesn't distinguish this batch operation from the single-lead creation sibling tool (crm_create_lead), which would be helpful for agent selection.

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?

The description provides no guidance on when to use this batch tool versus the single-lead creation tool (crm_create_lead), nor does it mention any prerequisites, constraints, or alternative batch tools for other CRM objects. The agent must infer usage from the name alone.

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