salesforce_bulk_update

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

With no annotations, the description carries the full disclosure burden. It correctly emphasizes that each record must include an 'Id' and states that per-record success status is returned, but it does not explain partial-failure behavior, field replacement semantics, or permissions. Useful but incomplete.

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?

Front-loaded with the core purpose, followed by a usage hint and well-structured Args/Returns sections. The example is compact and functional, with no filler or redundant content.

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 two-parameter bulk mutation with an output schema, the description covers the essential invocation details: object type, record list, required 'Id', and return shape. It could be more complete by addressing all-or-nothing behavior or batch limits, but it is sufficient for a typical agent to call it correctly.

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%, but the description compensates thoroughly: 'sobject' is defined with examples, and 'records' is explained with the mandatory 'Id' requirement and a concrete JSON example. This adds critical meaning beyond the bare schema.

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?

States a specific verb ('Bulk update') and resource ('multiple records'), and the name plus description clearly distinguish it from single-record update and bulk insert/delete siblings. The phrase 'many records' reinforces that this is the batch update variant.

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?

Explicitly says 'Use this to update many records efficiently', providing clear context for when to choose this tool. It does not name alternatives or state when not to use it, but the batch vs single-record distinction is unambiguous.

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