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 only states it's an update operation. It lacks critical behavioral details: whether it requires specific permissions, if it's idempotent, rate limits, error handling for partial failures, or what happens to unspecified properties. 'Update multiple contacts' implies mutation but offers no safety or operational context.

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?

Extremely concise with a single, clear sentence that front-loads the core action. No wasted words or redundant information, 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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't cover behavioral traits, error handling, or return values, leaving significant gaps for an AI agent to understand how to use it safely and effectively. The schema provides parameter details but doesn't compensate for missing operational context.

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 minimal value beyond the schema. It implies an array of contacts to update ('multiple contacts'), which aligns with the 'inputs' array in the schema, but doesn't explain parameter structure, required fields, or the meaning of nested properties. The schema documents all parameters thoroughly, so baseline 3 is appropriate.

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 understandable. It distinguishes from single-contact updates (e.g., crm_update_contact) by specifying 'multiple' and 'in a single request', but doesn't explicitly differentiate from other batch tools like crm_batch_update_companies.

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 on when to use this tool versus alternatives like crm_update_contact for single updates or other batch tools. The description mentions 'multiple contacts' but provides no context on prerequisites, limitations, or typical use cases.

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