connector_salesforce_bulk_ingest_results

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

The annotations already declare read-only and idempotent behavior; the description adds little beyond that. It mentions routing and the 'effect' parameter but does not explain return behavior, error conditions, or any side effects.

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 brief and uses a clean list format for parameters, making it easy to scan. It avoids unnecessary fluff, though this brevity sacrifices depth in several areas.

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?

Critical context is missing, such as what the tool returns, what the output schema represents, or how it fits into the bulk ingest workflow. It also does not differentiate from sibling tools, leaving the agent uncertain about when to invoke it.

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?

Since the schema has no descriptions, the parameter explanations in the description are the only source of semantics. While some entries like 'project_ref' and 'connector_account_ref' are helpful, others like 'arguments' are tautological and lack expected format or value detail.

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 mostly repeats the tool name and mentions routing but never clearly states that this tool retrieves bulk ingest results. It lacks a verb like 'retrieve' or 'get', making the purpose vague and indistinguishable from similar connector tools.

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 given on when to use this tool versus alternatives such as connector_salesforce_bulk_ingest_status or other Salesforce connector operations. There is no mention of prerequisites, typical scenarios, or how this tool fits into a larger workflow.

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