sf_create_records

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing any behavioral details, such as whether partial failures occur, what the 'confirm' parameter does, whether it supports bulk creation, or whether any targetOrg/directory context is required. For a mutating operation, this is a significant gap.

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, concise sentence that is easy to read, but it is under-specified. While it earns its place by stating the core action, it omits context and parameter details that could be included without much verbosity. It is not as concise as a well-structured description that front-loads critical information.

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?

With five parameters, no annotations, and no output schema, the description is far from complete. It does not explain required inputs, expected outcomes, or how it relates to the Salesforce environment (e.g., targetOrg, directory). This is inadequate for an agent to confidently select and invoke the tool correctly, especially given the large set of Salesforce sibling tools.

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%, and the description adds no explanation for any of the five parameters (confirm, records, directory, targetOrg, objectName). It only mentions 'records' implicitly through 'Create records,' but even that is more of the tool's purpose than a parameter explanation. The description does not compensate for the schema's lack of semantic detail.

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 tool's action: 'Create records in a Salesforce object using jsforce.' This uses a specific verb ('create') and resource ('records in a Salesforce object'), distinguishing it from sibling tools like sf_update_records, sf_delete_records, and sf_upsert_records. The mention of jsforce is an implementation detail but does not obscure the purpose.

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 such as sf_upsert_records or sf_update_records. It does not mention scenarios, prerequisites, or conditions that would make this tool preferable.

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