Three tools with clear verb-noun naming (search_content, list_sections, go_to) and reasonable descriptions (50-80 chars). All have input schemas with types. However, parameter descriptions are minimal or absent, output schemas are undocumented, and error handling guidance is missing. search_content lacks description for 'collection' and 'limit' parameters. No documentation of what fields are returned or how pagination works. Follows basic structure but lacks LLM-optimization depth expected of production tools.

• Document output schema for each tool. Specify exact fields returned (e.g., search_content returns [{title, url, description, collection}]). Include field types and whether fields are always present.
• Add descriptions to all parameters. For search_content: 'collection: Filter results to a specific content section (optional; omit to search all)' and 'limit: Maximum number of results (1-50, default 5)'.
• Specify pagination behavior. If search_content returns all results in one call, state 'Returns up to {limit} results; no pagination.' If paginated, add offset/cursor parameter and document total_count in response.
• Add error recovery guidance. E.g., 'If no results found, try a broader search term or call list_sections() to see available collections.' For go_to: 'If slug not found, call search_content() to find the correct page slug.'
• Document go_to side effects and add optional dry_run parameter or confirmation step. State whether navigation triggers analytics, modifies state, or has other consequences.