connector_salesforce_bulk_ingest_status

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful context that effect must be 'read' and that Spring verifies it, plus governance routing constraints. However, it does not explain what happens if required references are missing or what state inputs are needed beyond vaguely naming 'exact project/account' authority. No contradiction with annotations.

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 fairly compact and well-organized with a clear Args list. The front matter identifies the platform tool and the governance constraint early. Each parameter gets a single line, avoiding unnecessary prose. Minor deduction because the 'approval_ref' line is potentially distracting for a read-only status operation.

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?

Even though an output schema exists and annotations cover safety, the description is not complete enough for an agent to confidently select and invoke this tool. It lacks a plain-language statement of what the tool returns or checks, and it gives no workflow context tying it to bulk ingest create/upload/close/results. The parameter list is present, but the crucial 'arguments' content and the conditions under which this status call is valid are left unexplained.

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 carries the full burden for explaining parameters. It provides brief but meaningful semantics for all seven parameters, including 'Authenticated Project UUID,' 'Exact project correlation reference,' and 'Stable business-action identity.' The main weakness is that 'arguments' is only described as a 'JSON string of arguments for the connector operation' without specifying what fields the bulk_ingest_status operation expects inside that JSON.

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 only restates the tool name as 'Salesforce connector operation `bulk_ingest_status`' without defining what the operation actually does. The name strongly implies status retrieval, but the text never states the verb/resource clearly, such as 'Gets the current status of a Salesforce bulk ingest job.' It also does not distinguish this from sibling status tools like salesforce_bulk_query_status or connector_salesforce_bulk_ingest_results.

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 explicit guidance is given on when to use this tool versus alternatives. The description does not mention polling flows, prerequisites like an existing bulk ingest job, or relationship to sibling operations such as connector_salesforce_bulk_ingest_create and connector_salesforce_bulk_ingest_upload. It only says 'Routes only through the exact project/account governed connector authority,' which is an invocation constraint rather than usage guidance.

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