connector_salesforce_bulk_query_create

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

The description adds meaningful behavior beyond the annotations: it states that `effect` is a claimed read/write that Spring verifies, that `approval_ref` is needed when resuming a write, and that `idempotency_key` provides a stable business-action identity. This gives an agent important safety and approval context that the annotations alone do not 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?

The description is tight and front-loaded: one identity line, one routing/authority line, then a compact parameter list. Every bullet adds usable information without redundancy or filler.

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 parameter list and governance annotations are solid, and an output schema exists so return-value narration is not required. Still, the description never says what `bulk_query_create` actually performs in Salesforce, and it does not orient an agent to the natural follow-up workflow such as checking bulk query status or fetching results.

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 compensates by listing all seven parameters with practical meanings, including governance traits and approval behavior. The `arguments` parameter remains vague ('JSON string of arguments for the connector operation'), so the format and contents of the actual payload must be understood elsewhere.

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 identifies the tool precisely as the Salesforce connector operation `bulk_query_create` and names the underlying platform tool `salesforce.bulk_query_create`, so an agent can tell what domain and operation family it belongs to. It does not state the Salesforce-side meaning of creating a bulk query job, which keeps it short of a 5.

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 line 'Routes only through the exact project/account governed connector authority' implies this is the governed path for invoking a Salesforce operation, which gives minimal situational context. However, there is no explicit when-to-use vs. when-not-to-use guidance, and no mention of alternatives such as `connector_salesforce_bulk_query_status` or `salesforce_bulk_query_results`.

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