Bulk update Salesforce records

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

With no annotations, the description carries the full burden and does well: it discloses the endpoint, the 200-record cap, the required `Id` field, and the automatic splitting behavior. It does not cover partial-failure or response-shape behavior, which keeps it from a 5.

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?

Three short sentences, each earning its place: the core capability, the required record shape, and the automatic splitting behavior. No filler or repetition.

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?

All invocation-critical details are present: endpoint, batch size, `Id` requirement, auto-splitting, and the `allOrNone` option in the schema. The only notable gap is the lack of response/error shape, but since there is no output schema, this is a minor omission.

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 100%, so per the rubric the baseline is 3. The description reinforces that `records` entries need an `Id` plus changed fields and adds batch-size context, but it does not add meaning beyond what the schema already conveys.

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?

Clearly states the action ('update'), the resource ('Salesforce records'), and the distinguishing scope ('up to 200 records in one call', PATCH /composite/sobjects). The bulk nature separates it from single-record siblings like sf_update_record and from create/delete bulk 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?

Provides clear context by specifying a batch limit and noting that larger inputs are split automatically. It does not explicitly name alternatives or say 'use this tool instead of X', so it stops short of 5, but the intended use case is unmistakable.

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