Bulk Delete Records (Bulk API 2.0)

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

Beyond the destructiveHint annotation, the description adds valuable behavioral context: it is asynchronous, returns a job ID for tracking, and deleted records go to the Recycle Bin. It also includes a cautionary note. No contradiction with annotations.

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 concise and front-loaded with the core purpose, followed by a warning and return value. The parameter list is redundant with the schema but not harmful. Overall, it is appropriately sized, though the duplication slightly reduces efficiency.

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?

Given the absence of an output schema, the description adequately explains the key return value (job ID). It covers the async nature, the target resource, and the safety implication (Recycle Bin). For a bulk delete tool, this is complete enough for an agent to select and invoke it correctly.

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 input schema already provides complete descriptions for both parameters ('Object API name, e.g. 'Lead'' and 'Salesforce record IDs to delete'), and schema coverage is 100%. The description simply repeats the parameter names and types without adding extra semantic detail, so it adds no value beyond the 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 verb (deletes), the resource (multiple records by ID), the mechanism (Bulk API 2.0, asynchronous), and the return (job ID). This distinguishes it from sibling tools like sf_delete_record (single delete) and other bulk operations.

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 clear context: it is for asynchronous bulk deletion, which implies use when multiple records need to be removed. However, it does not explicitly name alternatives or contrast with single-record delete or bulk import/update, so it lacks explicit exclusions. Still, the context is clear enough.

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