This Salesforce MCP server has significant definition quality gaps. Tool naming is acceptable (verb_noun pattern followed), but descriptions are minimal and unevenly distributed. The first tool has NO description at all, violating the critical rule that every tool must have a non-empty description. The second tool has a basic description (36 chars) that meets the floor but lacks depth on when/why to use it. Parameter descriptions are present for the query_records tool but the listing tool has no parameters to describe. Output schemas are undocumented, LLMs cannot predict return structure. No error handling guidance is provided. The schema for query_records uses Zod validation (good), but lacks output type documentation. This server would not pass a production code review.

• Add a description to list_connected_salesforce_orgs: e.g., 'Retrieve a list of all connected Salesforce organizations and their metadata. Call this first to identify the target org for queries.' (60-80 chars).
• Expand query_records description to explain prerequisites: 'Execute a SOQL query against a connected Salesforce org. Requires a valid targetOrg name (from list_connected_salesforce_orgs). Use this to retrieve records matching specific criteria. Returns up to 10,000 records; use WHERE and LIMIT to control results.'
• Document the return type for both tools. Add a note like 'Returns: JSON object with org details and API metadata' for list_connected_salesforce_orgs and 'Returns: Array of record objects matching the SOQL query' for query_records.
• Add error handling guidance: 'If targetOrg is invalid, call list_connected_salesforce_orgs first to verify. If the query syntax is invalid, the Salesforce CLI will return an error message, adjust the WHERE or ORDER BY clause accordingly.'
• Implement result limiting and pagination: cap query_records at 500 returned records and document this in the description. If more are needed, guide the LLM to add LIMIT and OFFSET to the WHERE clause or use pagination. Update the limit parameter description to clarify it affects Salesforce SOQL, not the tool response.
• For query_records, add validation context to parameter descriptions: 'where: SQL WHERE clause conditions, e.g., "Status = \'Open\'" (ensure proper escaping). orderBy: Field name(s) to sort by, e.g., "CreatedDate DESC". limit: Max records to return (1 - 10000, default 100).'