This server has 9 tools with explicit Zod schemas and descriptions. Naming follows verb_noun patterns (dataform_help, dataform_compile, dataform_run), which is good. However, there are significant gaps: (1) Most tool descriptions are CLI-wrapper focused rather than explaining WHEN to use them or their prerequisites; (2) Parameter descriptions exist but are often minimal (10-40 chars) and lack constraints like min/max for numeric fields; (3) Output schemas are not formally documented, responses return 'content' and 'structuredContent' but the structure of structuredContent is not declared in a schema; (4) Error handling is minimal, no guidance on what to do if commands fail, no categorization of retryable vs fatal errors; (5) The server exposes 'projectDir' as implicit configuration rather than accepting it as a user-friendly parameter. These gaps prevent the server from reaching 70+.

• Formally document output schemas using JSON Schema. Define the structure of 'structuredContent' for each tool (e.g., dataform_compile returns {projectDir: string, summary: {counts: {tables: number, views: number, ...}}, graph: object, command: {args: string[], cwd: string}}).
• Expand parameter descriptions to 50-150 chars. For 'timeout' in dataform_test, replace 'Optional compilation timeout, e.g. `30s`, `2m` (`--timeout`).' with 'Maximum time to wait for Dataform compilation. Format: integer followed by unit (s/m/h), e.g. 30s, 2m. Compilation aborts if timeout is exceeded.'
• Add error handling guidance in tool descriptions. E.g., 'If compile fails, the response includes stderr with error details. Common causes: missing .df-credentials.json (run dataform_init_creds), syntax errors in .js files, or missing dependencies (run dataform_install).'
• Accept optional projectDir parameter in each tool to support multi-project workflows. Fall back to server config if omitted.
• Constrain numeric parameters. For actionRetryLimit, specify a maximum (e.g., max(10)) and document the default behavior when omitted.
• Add pattern validation to timeout parameter in dataform_test. Use a regex constraint or explicit format description to prevent invalid inputs like '30' (missing unit).
• Introduce a confirmation pattern for write operations (dataform_run, dataform_init_creds, dataform_install). Either add a 'dryRun' option or document that these tools execute immediately without confirmation.
• Return pagination hints when applicable. E.g., dataform_compile_action matches up to 20 actions but silently truncates beyond that. Add totalMatches field and pagination guidance.