salesforce_bulk_delete

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

With no annotations, the description carries the transparency burden. It does disclose the destructive operation and mentions per-record success status in Returns. However, it does not warn about irreversibility, permission requirements, or partial-failure behavior, which would be valuable for a delete tool with no annotation safety signals.

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 short, structured with Args/Returns, and front-loads the core purpose. The first two sentences slightly overlap ('Bulk delete multiple records' vs 'delete many records efficiently'), but the second does add usage context, so the redundancy is minor.

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 simple two-parameter tool with an output schema, this is largely complete: both arguments are explained, an example is provided, and return intent is stated. It lacks caveats like bulk limits, permanence, or authorization, but these are not defining for this tool's basic invocation.

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 fully explains both parameters: sobject as SObject type with examples, and record_ids as a list of record IDs with a concrete example. This is enough for an agent to construct a valid call.

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 a specific action and target: 'Bulk delete multiple records.' The word 'bulk' differentiates it from salesforce_delete_record, but it does not explicitly name or contrast that sibling, so it stops short of 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 sentence 'Use this to delete many records efficiently' provides a clear use case: many records, with efficiency as the reason. However, it does not state when not to use it or explicitly point to alternatives like salesforce_delete_record for single records.

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