salesforce_create_record

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic create action and does not disclose side effects (e.g., record ID assignment), permission requirements, error handling, or return format. The presence of an output schema is not leveraged in the description, leaving agents unaware of what the tool returns.

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 a single, clear sentence that immediately states the tool's action. It has no filler or redundant phrasing, making it highly concise and appropriately front-loaded with the verb 'Create'.

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?

Given the tool's 3 parameters, nested object in 'data', and the existence of sibling tools (especially bulk_create), the description is overly brief. It does not explain the expected structure of 'data' or how this tool compares to bulk creation. The output schema's presence might cover return values, but other contextual details (e.g., required field handling) are absent, making the description incomplete for an agent to invoke 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 schema description coverage is 0%, so the description must compensate for parameter meanings. It only references 'object_type' implicitly ('given object type') but does not explain 'data' (an object with additionalProperties) or 'org' (optional, default null). The description adds minimal meaning beyond the raw 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 clearly states the action ('Create') and the resource ('a new Salesforce record') with a qualifier ('of the given object type'). It distinguishes the tool from update/delete/query siblings by its create semantics, but does not explicitly differentiate from the sibling 'salesforce_bulk_create', relying on the tool name for that distinction.

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 provides no guidance on when to use this tool versus alternatives. It does not mention bulk_create for multiple records, nor does it note any prerequisites or context (e.g., needing a describe call first). The usage is implied ('create a record') but no exclusions or alternative comparisons are given.

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