salesforce_create_record

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

There are no annotations, so the description must carry the behavioral transparency burden. It discloses the write effect and the return shape (id, success, errors), which is useful, but it does not mention permission requirements, validation behavior, or failure modes beyond a generic 'errors' field. Adequate but not rich.

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 and well-organized into Args and Returns sections. Every line carries useful information, and the main purpose is stated first with 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?

For a two-parameter creation tool with an output schema, the description covers the essential invocation details: object type, field data, and expected response. It could add context about required Salesforce fields or validation behavior, but the description is otherwise complete enough for an agent to call the tool 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?

The input schema provides only names and types with 0% description coverage, so the description must compensate. It explains that 'sobject' is an SObject type with examples and that 'data' is key-value field values with a concrete example, adding real 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?

The description opens with a clear, specific verb and resource: 'Create a new Salesforce record.' It names the primary parameters and gives example object types, making the tool's purpose obvious and distinguishing it from update, delete, query, and upsert siblings.

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 says what the tool does but gives no guidance about when to choose it over alternatives such as salesforce_upsert_record or salesforce_bulk_insert. There are no exclusions, prerequisites, or context about when create is preferable to upsert.

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