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 for behavioral disclosure. While 'Update' implies a write/mutation operation, the description doesn't mention permission requirements, whether updates are atomic or partial, error handling for failed updates, rate limits, or what happens to unspecified contact properties. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise at just 6 words, front-loading the core functionality ('Update multiple contacts') without any wasted words. Every word earns its place, though this conciseness comes at the expense of completeness.

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 mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is severely incomplete. It doesn't address critical context like authentication requirements, mutation consequences, error handling, or response format. The description fails to provide the necessary information for safe and effective tool invocation.

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 schema has 0% description coverage, meaning no parameters are documented in the schema. The description mentions 'multiple contacts' which hints at the 'inputs' array parameter, but provides no details about the structure of contact objects, required fields like 'id', or the meaning of properties like 'leadstatus' and 'lifecyclestage'. The description doesn't 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 ('Update') and resource ('multiple contacts'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'crm_update_contact' (single contact update) or other batch update tools like 'crm_batch_update_companies', leaving some ambiguity about when to choose this specific batch contact tool.

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. With multiple sibling tools including 'crm_update_contact' (single contact), 'crm_batch_update_objects' (generic batch), and 'crm_batch_update_companies' (other entity type), there's no indication of when batch contact updates are preferred over individual updates or other batch operations.

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