sf_delete

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

No annotations are provided, so the description carries full burden. It discloses that the delete is immediate but recoverable for 15 days via Recycle Bin, and mentions preview mode. This sufficiently conveys the destructive nature and recovery mechanism.

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 at 5 lines, front-loaded with the purpose, and every sentence contributes essential information. No redundancy.

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 3-param required tool with no output schema, the description covers all key aspects: purpose, parameter roles, safety, and preview. Minor omission of return value specification, but adequate for agent 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 coverage is 100%, baseline is 3. The description adds value by explaining the confirm parameter's behavior (preview vs execute) and provides concrete examples, exceeding the schema's minimal descriptions.

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 starts with 'Delete a Salesforce record by Id.' which clearly identifies the verb (delete), resource (Salesforce record), and method (by Id). It distinguishes from siblings like sf_create, sf_update, and sf_read, and also from delete tools for other systems.

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?

Explicit safety instructions explain when to pass confirm=true vs false, including the preview mode. This provides clear guidance on usage context. It does not directly compare with alternative tools, but the safety emphasis compensates.

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