Two tools with minimal schema documentation and weak descriptions. soqlQuery has a basic string parameter but no output schema documented. updateSobjectRecord has three parameters (sobject-name, id, body) with descriptions present but lacks output schema. Neither tool description explains what data is returned, when to use each tool, or error recovery paths. No parameter constraints (enums, ranges, patterns). No idempotency hints despite updateSobjectRecord being a write operation. Descriptions are functional but generic (72-85 chars), below the 194-char baseline for production tools. No evidence of input validation, error categorization, or recovery guidance in the source code.

• Add explicit output schema for soqlQuery: document that it returns {records: [{Id, Name, ...fields from query}], totalSize: number}. Include pagination guidance if result sets can exceed 50 records.
• Document updateSobjectRecord response: {success: boolean, id: string, updatedFields: {[fieldName]: newValue}}. Add error cases: 'Record not found', 'Invalid field name', 'Permission denied'.
• Add idempotentHint: true to updateSobjectRecord schema, or document that repeated calls with identical body are safe. If not idempotent, add a confirmation step or dry-run parameter.
• Expand tool descriptions to 150+ characters. Include WHEN to use each tool (e.g., 'Use soqlQuery to retrieve Salesforce records; use updateSobjectRecord to modify existing records'). Add dependency hints: 'If you only have a record name, call soqlQuery first to find the ID.'
• Add parameter constraints: soqlQuery.q should document max length and forbidden keywords (e.g., 'SOQL query string, max 4000 chars, must include LIMIT clause'). updateSobjectRecord.sobject-name should be an enum of valid types (Account, Case, Opportunity, etc.) or reference a discovery tool.