salesforce_bulk_query_results

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

The description gives minimal behavioral information, only noting that it routes through an API under JWT/tenant/company scope. It does not disclose that the tool likely reads query results, nor does it mention any safety or mutability aspects. Since no annotations are provided, the description should have filled this gap but fails to do so.

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 concise with only a few lines, which is structurally fine. However, the content is too sparse to be useful; it prioritizes brevity over informativeness. An adequate description would be similarly concise but more informative.

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 tool's complexity (one parameter, no annotations, output schema not described), the description is completely inadequate. It does not explain the return value, required input structure, or any constraints, leaving too much unspecified for an agent to use correctly.

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 'arguments' is described as a 'JSON string of arguments for the connector operation,' which adds no meaningful information beyond the schema. The description does not specify what keys the JSON should contain (e.g., jobId), making it impossible for an agent to construct the correct input. With 0% schema description coverage, the description fails to compensate.

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 merely states 'Salesforce connector operation bulk_query_results' and mentions routing through an API, but does not explicitly state that the tool retrieves results of a bulk query. The name implies this, but the description lacks clarity and does not differentiate from siblings like salesforce_bulk_query_create or salesforce_bulk_query_status.

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. It does not explain prerequisites, context, or conditions under which this tool should be invoked, leaving the agent without decision-making information.

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