salesforce_update_records

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

Goes well beyond the annotations by disclosing atomicity ('all or none', a key matching none or several refuses the whole call), no-op handling, partial-field update semantics, match resolution via key_field, and the return payload shape. These are the exact behaviors annotations (readOnly/idempotent/destructive) cannot express.

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-loads the core behavior (batch update, all-or-none) in the first sentence, then conditions, then return shape, then sibling routing. Every clause carries information and nothing is repeated from the schema.

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 batch mutation tool with no output schema, the description supplies the batch limit, atomicity, error/abort conditions, approval requirement, and the return keys ({object_type, updated, ids}). An agent has everything needed 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 coverage is already 100%, so the baseline is 3, but the description adds meaning the schema does not: key_field defaults to Id or an External ID-marked field and 'is never changed itself', plus that only listed fields change and null clears a field. That is genuine semantic enrichment beyond the schema text.

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 and resource with exact scope: change 1 to 200 existing records of one Salesforce object type. It differentiates itself from siblings by contrast ('Use salesforce_update_record for one record by id'), so an agent can pick the bulk vs. single variant without opening a schema.

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 routes to alternatives: salesforce_update_record for a single record by id and salesforce_search to find ids. It also names the prerequisite ('Requires user approval') and the batch-size window, giving the agent clear conditions for when this tool applies.

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