crm_batch_delete_objects

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't mention critical aspects like whether deletions are permanent or reversible, what permissions are required, rate limits, error handling for partial failures, or what happens to associated data. For a destructive batch operation, this represents significant gaps in behavioral 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?

The description is extremely concise at just 7 words, front-loading the core action ('Delete multiple CRM objects') with the operational context ('in a single request'). Every word serves a purpose with zero redundancy or unnecessary elaboration, making it efficient for quick comprehension.

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 destructive batch operation with no annotations, no output schema, and 0% parameter documentation in the schema, the description is inadequate. It doesn't explain what happens after deletion (success indicators, error responses), doesn't clarify parameter usage, and provides no safety warnings or behavioral context that would help an agent use this tool correctly and safely.

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?

With 0% schema description coverage for both parameters, the description provides no information about what 'objectType' and 'objectIds' represent or how they should be used. The description doesn't mention the available object types (visible in the schema enum) or explain the format/requirements for object IDs. For a tool with two required parameters, this leaves the agent guessing about proper usage.

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 ('Delete') and resource ('multiple CRM objects') with the operational context ('in a single request'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'crm_delete_object' (singular delete) or other batch operations like 'crm_batch_update_objects', leaving some ambiguity about when to choose this specific batch deletion 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 siblings like 'crm_delete_object' (singular delete), 'crm_batch_delete_associations', and various other batch operations, there's no indication of appropriate use cases, prerequisites, or trade-offs between batch and individual deletion methods.

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