Critical gaps across all dimensions. Tool descriptions are present but generic (avg ~50 chars, well below 194-char baseline). Parameter descriptions exist in schemas but are minimal. No input schemas visible in source code for most tools, only Zod schema exports shown, not actual tool registration. Output schemas undocumented. Error handling absent. No tool annotations (readOnlyHint/destructiveHint). Composition is reasonable (29 focused tools), but definition quality is significantly below production baseline.

• Add explicit input schemas to every tool registration in src/tools/*.ts. Each schema must include parameter types, descriptions (50-200 chars), constraints (enums, min/max), and examples. Use Zod's .describe() method consistently.
• Expand tool descriptions to 100-200 characters. Template: '[VERB] [OBJECT]. Use this to [WHEN]. Returns [WHAT]. Requires [PREREQ].' Example: 'Create a new collection in your Webflow site. Use this to organize content items. Returns collection ID and field schema. Requires site_id.'
• Add tool annotations via MCP's readOnlyHint/destructiveHint. Mark delete_collection_item, delete_script, publish_collection_item, publish_site as destructiveHint=true. Mark all list_* and get_* as readOnlyHint=true.
• Document output schemas for each tool. Add a 'Returns' section to descriptions or create a separate schema document. Include field names, types, and which fields are needed for chaining (e.g., collection_id for list_collection_items).
• Implement error handling with recovery guidance. Catch API errors and return structured responses: {error: 'User not found', suggestion: 'Try search_users() with a partial name', retryable: false}. Guide LLMs on next steps.