salesforce_bulk_insert

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

With no annotations, the description carries the behavioral burden, and it does well by disclosing that the Bulk API processes records in batches and returns per-record success, id, and errors. It does not mention rate limits, permissions, or asynchronous timing, but the core operation and result behavior are clearly communicated.

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 well-structured with a clear purpose sentence, one usage sentence, and organized Args/Returns sections. Every sentence adds value, and there is no unnecessary repetition or fluff.

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 tool with two required parameters, no schema descriptions, and no annotations, the description provides sufficient detail to invoke it correctly and interpret results. Some additional context such as maximum batch size, object restrictions, or asynchronous behavior would be useful, but it is not essential for correct basic 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 input schema provides no property descriptions (0% coverage), but the description fully compensates by explaining sobject with examples and defining records as a list of field-value dicts with a concrete example. This gives an agent everything needed to construct valid arguments.

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 'Bulk insert multiple records,' which names a specific action and resource. It also clarifies the scope by emphasizing multiple records and high volumes, distinguishing it from sibling tools like salesforce_create_record or bulk update/delete tools.

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 description explicitly says 'Use this to create many records efficiently' and states it is 'optimized for high volumes,' giving clear contextual guidance for when to use it. It does not explicitly name alternatives or provide exclusion criteria, which prevents a 5.

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