Four tools with basic verb-noun naming (search_site, get_page_content, list_content, get_sitemap). All have short descriptions (10 - 50 chars) and input schemas with type definitions. However, descriptions lack depth, they do not explain WHEN to use each tool, dependencies, or error recovery. Parameter descriptions are minimal (e.g., 'Search query, 1 - 500 code points' lacks context on what 'search' means in this domain). Output schemas are not documented. No error handling guidance. Schemas are present but sparse; list_content lacks enum for 'type' parameter, inviting invalid values. Overall: functional but below production baseline (194 chars avg description; 100% of A+ tools document outputs).

• Expand each tool description to 100 - 200 chars. Include: what it does, when to use it (vs similar tools), and what it returns. E.g., 'Search the site for public URLs and content snippets matching a query. Use this to discover pages before fetching full content with get_page_content. Returns up to 50 results with URL and snippet preview.'
• Document output schemas for all tools. Specify: field names, types, and whether they are always present. E.g., search_site returns [{url: string, snippet: string, relevance: number}].
• Add enum constraint to list_content 'type' parameter. Enumerate valid content types (e.g., 'blog_post', 'documentation', 'product_page') to prevent invalid queries.
• Add error recovery hints to descriptions. E.g., 'If no results found, try a broader query or use list_content to browse all available content.'
• Clarify parameter constraints in descriptions. For get_page_content, explain: 'same-site only means the URI must be on the same domain as the Netlify site; external URLs are rejected to prevent SSRF attacks.'