Three tools with complete schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tools have names starting with action verbs (datasets, query, metadata) and descriptions (avg 180 chars, within baseline 194). However, parameter descriptions lack detail on constraints, formats, and valid ranges. Output schemas are not documented, LLMs cannot predict response structure for downstream chaining. No error handling guidance. The 'query' tool accepts free-form SoQL strings without validation hints, inviting malformed queries.

• Document output schemas for all three tools. Example for datasets: 'Returns {results: [{resource_id, name, description, category, updated_at}], total_count}'. Example for query: 'Returns array of row objects matching SoQL query, e.g. [{name, amount, date}, ...]'.
• Add min/max constraints to numeric parameters in schema. For datasets limit: add 'minimum': 1, 'maximum': 100. For query limit: add 'maximum': 1000 or document Socrata's default.
• Enhance SoQL parameter descriptions with syntax hints and examples. E.g., where: 'SoQL $where filter (e.g., "year >= 2020 AND status = \'Active\'"). Use column names from metadata tool. Operators: =, !=, >, <, >=, <=, AND, OR, NOT, IN, LIKE.'
• Add error recovery guidance. Wrap fetch calls in try-catch with specific error messages: 'Dataset not found (404). Verify resource_id with datasets tool.' or 'Query syntax error (400). Check SoQL syntax at dev.socrata.com/docs/queries.'
• Document required vs optional parameters more explicitly. Mark resource_id as required in query and metadata (already done). For datasets, clarify that query is optional (search all if omitted).