crm_batch_delete_objects

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 'Delete' clearly indicates a destructive operation, the description lacks critical details: 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 with zero annotation coverage, this is a significant gap.

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 communicates the core purpose without waste. It's appropriately sized for a tool with a straightforward name and clear action, though the brevity contributes to gaps in other dimensions.

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 2 parameters (0% schema coverage), no annotations, and no output schema, the description is incomplete. It lacks critical context about behavioral implications, parameter usage, error handling, and differentiation from sibling tools. The agent would struggle to use this tool correctly without additional information.

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 but provides no parameter information. It doesn't explain what 'objectType' represents (the enum values like 'companies', 'contacts'), what format 'objectIds' should be in, or any constraints (e.g., maximum batch size). With 2 undocumented parameters, the description adds no value beyond what the bare schema provides.

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 ('Delete multiple') and resource ('CRM objects'), and specifies it's done 'in a single request', which adds useful context about batch operation. However, it doesn't differentiate from sibling tools like 'crm_delete_object' or 'crm_batch_delete_associations', which would require more specificity about what distinguishes this batch deletion from those alternatives.

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 like 'crm_delete_object' (single deletion) or other batch operations. There's no mention of prerequisites, limitations, or appropriate contexts for batch deletion versus individual deletions, leaving the agent with insufficient usage context.

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