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 implies a write operation ('create') but doesn't disclose critical traits like permissions required, whether it's idempotent, error handling for partial failures, rate limits, or what the response contains. For a batch mutation tool, this is a significant gap in transparency.

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 and appropriately sized for the tool's purpose, making it easy to parse quickly.

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), lack of annotations, and no output schema, the description is incomplete. It fails to address behavioral aspects, usage context, or response format, leaving the agent under-informed for safe and effective tool invocation in a CRM system.

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?

The description mentions 'multiple leads' but doesn't explain the parameter structure. The input schema has 1 parameter (inputs) with 0% description coverage, and the description adds no details about the array format, required fields, or the nested properties/associations. However, since the schema is detailed (showing lead properties and associations), the baseline of 3 is appropriate as the schema does the heavy lifting, though the description adds no value.

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 'Create multiple leads in a single request' clearly states the action (create) and resource (leads), with the batch aspect distinguishing it from single-create tools like crm_create_lead. However, it doesn't explicitly differentiate from other batch create tools (e.g., crm_batch_create_companies, crm_batch_create_contacts), which would be needed for a perfect score.

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 (e.g., rate limits, batch size), or comparisons to single-create (crm_create_lead) or other batch operations. This leaves the agent without context for tool selection.

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