Three tools with clear, focused responsibilities and complete input schemas. Tool names are action-oriented (datasets, query, metadata). Descriptions are present and moderately detailed (100-180 chars), explaining what each tool does and when to use it. All parameters have type definitions and descriptions. However, output schemas are not documented, LLMs cannot predict response structure for downstream planning. Parameter descriptions lack constraints (e.g., 'limit 1-100' is stated but not enforced in schema; SoQL syntax examples could mislead). No error handling guidance or recovery paths. Missing idempotency hints and field-chaining documentation.

• Document output schemas for all three tools. For 'datasets', specify: {results: [{resource_id, name, description, category, updated_at}], total_count}. For 'query', specify: {rows: [object], count}. For 'metadata', specify: {columns: [{name, type}], row_count, category, last_updated}.
• Add JSON Schema constraints: datasets.limit with minimum: 1, maximum: 100; query.limit with maximum: 1000. Remove prose constraints from descriptions.
• Add error handling guidance in tool descriptions: 'If resource_id is invalid, call datasets() to search for the correct ID.' Include common SoQL errors (syntax, column not found).
• Document the tool chain explicitly: 'Use datasets() to search for a resource_id, then pass it to query() or metadata().' This guides multi-step planning.
• Replace SoQL syntax examples with links to Socrata documentation or formal grammar. E.g., 'SoQL $where filter (see https://dev.socrata.com/docs/queries)' instead of inline examples.