salesforce_bulk_query_create

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions routing details but fails to explain what the tool actually does (e.g., creates a query job, runs it, etc.), side effects, or auth requirements beyond the JWT scope.

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 short (3 sentences) and structurally adequate, but it sacrifices substance for brevity. While concise, it lacks critical details, making it less useful overall.

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 complexity of Salesforce bulk operations and the presence of sibling tools for status and results, the description fails to explain the workflow (e.g., create query, then poll status, then retrieve results). The agent cannot infer how to use this tool correctly without additional context.

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 only parameter is 'arguments' (string). The description adds that it is a JSON string of arguments for the connector operation, which provides minimal clarity. However, schema coverage is 0%, and the description does not specify expected keys or format, leaving the agent without enough information to construct valid input.

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?

Description states it's a Salesforce connector operation for bulk_query_create, indicating it creates a bulk query. However, it doesn't explain what a bulk query is or how it differs from sibling tools like salesforce_bulk_ingest_create or salesforce_bulk_query_results, leaving the purpose somewhat vague.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or when not to use it. The description lacks any context for decision-making.

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