sf_delete_record

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

No annotations are provided, so the description must disclose consequences and context. It only states the raw operation and gives no information about permanence, Salesforce recycle-bin behavior, required permissions, failure behavior, or return value. For a destructive operation, this is a significant transparency 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 very brief and front-loaded, with no wasted words. It conveys the primary action immediately, though the extreme brevity contributes to the lack of contextual detail penalized elsewhere.

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 tool with no annotations, no output schema, and no parameter documentation, a single sentence is insufficient. Key context is missing: what object type is targeted, what happens after deletion, whether it is recoverable, and what response the agent should expect.

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%, yet the description adds no real parameter meaning. 'By ID' merely restates the 'Record Id' property name, and the required 'sobject' parameter is not explained at all, leaving the agent to guess its format and purpose.

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 names the specific verb 'Delete' and the resource 'a record by ID,' which clearly states the tool's core function. It is naturally distinguished from siblings like sf_get_record, sf_update_record, and sf_query because deletion is a distinct operation.

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?

There is no guidance about when to choose this tool over alternatives, when not to use it, or how it relates to sibling tools like sf_bulk_load or sf_composite. The intended use must be inferred entirely from the name and the one-line description.

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