The server exposes 35 tools with basic structure but significant quality gaps. Tool names follow verb_noun patterns (e.g., sites_list, cms_collection_item_create) which is positive. However, ~60% of tools have incomplete or missing parameter descriptions. Input schemas are present for many tools but lack depth, most show only siteId and collectionId with minimal context. Several tools (e.g., cms_collection_item_create, de_element_create, de_element_update, webhooks_create) accept 'fieldData' or similar object parameters with type:object and no nested schema definition, making it impossible for LLMs to know what fields are valid. Descriptions are present but often generic (e.g., 'Create a new item in a collection', 17 characters, below the 10-1024 target but borderline). No visible error handling guidance, no output schema documentation, and no indication of idempotency or state-modification semantics. Tool composition is reasonable (single responsibility, chainable via siteId), but the lack of detailed parameter specs and output documentation severely limits LLM usability.

• Add complete nested schema definitions for all object parameters. For cms_collection_item_create, replace 'fieldData: { type: object, description: Field data for the item }' with explicit properties like 'fieldData: { type: object, properties: { name: { type: string, description: Item name }, ... }, required: [name] }'. Reference Webflow CMS API docs to populate valid field names per collection type.
• Document output schemas for all tools. For sites_list, specify: 'Returns an array of objects with fields: [{ siteId: string, name: string, displayName: string, createdOn: number }]. Includes pagination metadata if applicable: { sites: [...], total: number, hasMore: boolean }'.
• Implement pagination parameters (limit, offset) for all list tools with a default limit of 20 and max of 100. Update descriptions to state: 'Returns up to 20 sites per request. Use limit (1-100) and offset for pagination. Returns total count for planning subsequent calls.'
• Extend descriptions to 50-150 characters with context. Instead of 'List all sites accessible to the authenticated user', write: 'List all Webflow sites you can access. Use this to discover siteId for other tools. Returns site metadata including creation date and display name.'
• Add error handling to tool implementations with actionable guidance. E.g., if siteId is invalid, return: 'Site not found. Call sites_list to see available sites, or verify siteId format.' Document this in tool descriptions.
• For destructive tools (delete operations), add a 'dryRun' boolean parameter (default false) or require explicit 'confirm: true' parameter. Update descriptions to warn: 'WARNING: This permanently deletes the item. Pass confirm=true to proceed. Consider exporting data first.'