delete-record

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

With no annotations, the description carries full burden. It mentions 'auto-bulk switching' but does not explain behavior such as idempotency, error handling when records don't exist, or how the `allOrNone` option affects outcome. This omission leaves the agent uncertain about side effects.

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, front-loaded sentence that efficiently conveys the tool's primary action and unique feature. No redundant words.

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 tool has 3 parameters including a nested options object and no output schema, the description is too sparse. It omits return values, error behavior, and details on how auto-bulk switching works, leaving the agent with insufficient context for correct usage.

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 description adds no information about parameters beyond what the input schema already provides. The schema has 67% coverage (sobjectType and recordIds described, options object lacks its own description), yet the description does not compensate for the missing options description or clarify how recordIds handles single vs. bulk.

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 'Delete records by ID(s) with auto-bulk switching' clearly states the verb (delete), resource (records), method (by ID(s)), and a distinguishing feature (auto-bulk). It differentiates from sibling tools like create-record or update-record.

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 tool's purpose is clear and it has no sibling delete tools, so usage is straightforward. However, the description lacks explicit guidance on when not to use it (e.g., for soft-delete scenarios) or prerequisites (e.g., sharing rules).

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