salesforce_delete_record

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

With no annotations, the description carries the full behavioral burden, but it only says deletion returns a success status. It does not disclose that deletion is typically irreversible, whether special permissions are needed, or what happens when the record does not exist. This is thin for a destructive operation.

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 compact and well structured with Args and Returns sections. It front-loads the purpose and contains no filler, repetition, or irrelevant detail.

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?

The two parameters are well described and an output schema exists, so basic invocation is covered. However, the definition omits important context for a delete tool: irreversibility, permission needs, and the distinction between this single-record delete and the sibling salesforce_bulk_delete. These gaps keep it from being fully complete.

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 add meaning, and it does: it defines 'sobject' as an SObject type with concrete examples and 'record_id' as an 18-character Salesforce ID. This goes well beyond the bare string types in the schema, though it could still add format constraints or valid object names.

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 opens with 'Delete a Salesforce record', a specific verb and resource that clearly distinguishes this from siblings like salesforce_create_record, salesforce_update_record, and salesforce_bulk_delete. The singular 'a record' further signals single-record deletion rather than 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 phrase 'a Salesforce record' implies this tool is for deleting one record at a time, which provides some usage signal against the bulk sibling. However, it does not explicitly state when to prefer this over salesforce_bulk_delete or mention any preconditions, so the guidance remains implicit.

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