salesforce_bulk_ingest_create

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

Annotations already signal a non-readonly, destructive operation, and the description adds useful context that calls route through the domain-agent dispatcher under JWT, tenant, and company scope. However, it does not disclose what the create action actually changes or destroys, whether it is asynchronous, or what side effects might follow.

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 compact, front-loaded with the action name, and contains a clear Args list without filler. The first sentence is somewhat redundant with the tool name, but the routing explanation and argument definitions are economically written.

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?

The presence of an output schema covers return-value expectations, so that omission is acceptable. But the description leaves out the domain purpose, the bulk-ingest workflow context, and what constitutes a valid message or structured input for this action. Given destructiveHint=true and openWorldHint=true, this missing context is significant.

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%, so the description must carry the parameter meaning. It adds that message is a 'free-text objective' and inputs is an 'Optional JSON string of structured inputs,' which is slightly more than the bare schema, but it gives no examples, accepted keys, or action-specific structure. An agent still cannot determine what valid inputs or messages look like for this specific bulk ingest action.

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 essentially says 'Run the salesforce domain agent action bulk_ingest_create,' which restates the tool name without explaining what that action accomplishes. It adds dispatcher routing and scoping context, but an agent still cannot tell that this creates or initializes a Salesforce bulk ingest job or distinguish it from siblings like salesforce_bulk_ingest_upload, status, results, and close.

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?

There is no when-to-use guidance, prerequisite information, or mention of alternative tools. The description does not explain how this tool relates to the other salesforce_bulk_ingest_* lifecycle tools or when to choose it over connector_salesforce_bulk_ingest_create or salesforce_bulk_query_create. The routing/scope sentence is about mechanism, not usage conditions.

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