crm_batch_update_contacts

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 ('Update') but doesn't disclose critical traits like required permissions, whether updates are partial or full, error handling for invalid inputs, rate limits, or what the response contains. This leaves significant gaps for a mutation tool.

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 front-loaded with the core action and efficiently conveys the batch nature. Every word earns its place, 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 mutation tool with 1 parameter but deeply nested schema), lack of annotations, and no output schema, the description is insufficient. It doesn't address behavioral aspects like side effects, error handling, or response format, leaving the agent with inadequate context to use the tool safely and effectively.

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 schema provides no parameter descriptions. The description adds no parameter-specific information beyond implying an array of contact updates. It doesn't explain the 'inputs' structure, required 'id' field, or the 'properties' object with its many fields. Baseline 3 applies as it minimally compensates for the coverage gap.

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 ('Update') and resource ('multiple contacts'), making the purpose immediately understandable. It distinguishes from single-contact update tools by specifying 'multiple contacts in a single request', though it doesn't explicitly differentiate from sibling batch tools like crm_batch_update_companies or crm_batch_update_leads.

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. It doesn't mention prerequisites (e.g., contact IDs must exist), compare to single-contact updates (crm_update_contact), or specify limitations like batch size constraints. The description only states what it does, not when to choose it.

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