crm_batch_update_objects

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 'Update multiple CRM objects' which implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether updates are atomic/partial, error handling for failed items, rate limits, or what the response contains. This is inadequate for a batch 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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded with the core functionality.

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 2 parameters (one with enum), 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't address key contextual aspects like what object types are supported (though hinted in schema), update behavior, error handling, or output format, leaving significant gaps for the agent.

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 CRM objects' which hints at the 'inputs' array parameter, but doesn't explain what 'objectType' is, the structure of 'inputs' items, or the meaning of 'properties' within them. The description adds minimal value beyond the bare 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 ('Update multiple') and resource ('CRM objects') with the scope 'in a single request', which is specific and informative. However, it doesn't explicitly distinguish this tool from sibling batch update tools like crm_batch_update_companies or crm_batch_update_contacts, which would require a 5.

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 many sibling tools including specific batch updates (e.g., crm_batch_update_companies) and single-object updates (e.g., crm_update_object), the agent has no indication of when this general batch tool is preferred over more specific ones.

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