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 but offers minimal behavioral insight. It confirms a write operation ('Create') but doesn't disclose permissions needed, rate limits, error handling for partial failures, or what the response contains. For a batch mutation tool, this lack of context 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 and context, making it easy to parse quickly without unnecessary elaboration.

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, and no output schema, the description is inadequate. It lacks details on behavioral traits, parameter usage, error handling, and response format, leaving the agent under-informed for a complex mutation operation.

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 details beyond implying an array input for 'multiple leads'. It doesn't explain the 'inputs' structure, required fields like 'properties', or optional ones like 'associations'. The schema provides rich detail, but the description doesn't compensate for the coverage gap, resulting in a baseline score.

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') with the specific context of batch processing ('in a single request'). It distinguishes from single-create tools like 'crm_create_lead' by emphasizing batch capability, though it doesn't explicitly differentiate from other batch 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 compare it to single-create ('crm_create_lead') or other batch tools (e.g., 'crm_batch_create_companies'), leaving the agent to 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.