salesforce_bulk_query_status

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

Without annotations, the description must disclose behavioral traits. It only mentions routing and a generic 'arguments' parameter, giving no information about what the tool does, side effects, or expected behavior. The agent has no way to infer that this is a read-only status check.

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 but not concisely informative. It wastes space on redundant routing information ('Routes through /api/tools/invoke under your JWT, tenant, and company scope') while omitting essential purpose and usage details. It is under-specified rather than 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?

Given the lack of annotations, minimal schema coverage, and no output schema description, the description fails to provide enough context for an agent to use the tool correctly. It does not explain the relationship to other bulk operations or what the status response contains.

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' (a JSON string). The description says it contains 'arguments for the connector operation' but provides no details on its structure or required fields. With 0% schema coverage and no elaboration in the description, the agent cannot properly construct the parameter.

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 restates the tool name ('Salesforce connector operation `bulk_query_status`') without explaining what the tool does. It fails to specify that it checks the status of a Salesforce bulk query job, leaving the agent without a clear purpose.

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 is provided on when to use this tool versus alternatives. Sibling tools like 'salesforce_bulk_query_create' and 'salesforce_bulk_query_results' exist, but the description does not differentiate them or explain the workflow context.

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