crm_batch_create_contacts

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 operation but doesn't disclose behavioral traits like whether it's idempotent, what permissions are required, how failures are handled in batch, rate limits, or what the response looks like. This is inadequate for a mutation tool with complex inputs.

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, clear sentence with zero wasted words. It's appropriately sized and front-loaded, efficiently conveying the core purpose 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?

Given the complexity (1 parameter with deeply nested structure, 0% schema coverage, no output schema, no annotations), the description is severely incomplete. It doesn't explain the input format, output, error handling, or behavioral context needed for a batch creation tool 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'multiple contacts' which hints at an array input, but provides no details about the structure, required fields, or semantics of the 'inputs' parameter and its nested properties/associations. The description adds minimal value beyond the schema.

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 contacts') and the resource ('contacts'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'crm_create_contact' or 'crm_batch_create_companies' beyond the obvious 'contacts' vs 'companies' difference, missing explicit differentiation.

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 tool versus alternatives like 'crm_create_contact' (single contact creation) or other batch tools. It lacks context about prerequisites, performance considerations, or error handling for batch operations.

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