salesforce_bulk_ingest_create

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

No annotations are provided, and the description only mentions routing and authentication ('Routes through... under your JWT...'). It does not disclose what the tool actually does (e.g., creates a job, requires further steps). Behavioral traits are almost entirely absent.

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 (two sentences plus args listing) but contains redundancy: the first two sentences both name the tool. The routing info takes space without adding functional value. Could be more concise.

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?

Despite having an output schema (unknown content), the description fails to explain the tool's role in the bulk ingest workflow (e.g., must be followed by upload, close). The parameter is not elaborated, and no return value hints are given. Incomplete for a multi-step process.

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 single parameter 'arguments' is described as 'JSON string of arguments for the connector operation', which adds minimal meaning beyond the schema's type and title. With 0% schema coverage, the description should explain expected keys but does not.

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 states 'Salesforce connector operation `bulk_ingest_create`' which is vague and does not explain what the tool does beyond its name. It does not specify that it creates a bulk ingest job or what that entails. This is only slightly better than a tautology.

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 sibling tools like salesforce_bulk_ingest_upload or salesforce_bulk_ingest_close. No context about prerequisites or workflow phase is given.

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