salesforce_bulk_query

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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose that the Bulk API is asynchronous and optimized for large volumes, which are important traits. However, it does not explain what 'asynchronous' means for the caller—whether it returns a job ID, whether it polls to completion, or how results are delivered—and simply says 'Returns: List of all matching records,' which could be misleading if results are not returned synchronously.

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 and well organized: a one-line summary, a usage condition, an important behavioral note, and clearly labeled Args/Returns sections. Every sentence contributes useful information, and the key usage threshold is front-loaded.

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?

For a two-parameter tool with an output schema available, the description covers the essential invocation details: what to pass, when to use it, and what to expect back. The main gap is the incomplete elaboration of asynchronous behavior and result retrieval, which is relevant for an agent deciding whether to call this versus a simpler tool.

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 compensate for the bare input schema. It does so by defining 'sobject' with a concrete example ('Account', 'Contact') and 'soql' as a SOQL query string. This gives the agent enough meaning to invoke the tool correctly, though it could add more detail about SOQL expectations or validation.

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 executes a bulk query for large data sets, names the specific resource (Bulk API), and distinguishes it from the regular salesforce_query by the 2,000-record threshold. An agent can tell exactly what this tool does and how it differs from its siblings.

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 gives a concrete selection criterion: use this for queries that may return more than 2,000 records. This effectively tells the agent when to prefer this over the standard query tool. It does not explicitly name alternative tools or mention when not to use it, but the threshold provides clear contextual guidance.

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