Three tools with basic descriptions and partial schemas. fetch_product_page and extract_product_info have clear, actionable descriptions (120-150 chars) and simple input schemas with type and description for each parameter. generate_presentation_slide has a more complex schema with object-type parameters that lack internal field documentation. No output schemas documented for any tool. Error handling is present in code (handle_fetch_errors decorator) but not surfaced in tool definitions. Parameter descriptions are adequate but lack constraints (enums, ranges, format specs). No tool annotations (readOnlyHint, idempotentHint). Naming is verb-noun compliant but generic ('fetch', 'extract', 'generate').

• Add enum constraint to generate_presentation_slide's 'slide_type' parameter: ['cover', 'journey_map', 'donut', 'comparison', 'metric_grid', 'testimonial', 'cta'].
• Document the internal structure of 'data' and 'theme' objects in generate_presentation_slide. Specify required vs optional fields, types, and examples for each slide_type variant.
• Add output schema documentation to all three tools. Example: fetch_product_page returns {html: string, status: 'success'|'blocked'|'timeout', warning?: string}.
• Add readOnlyHint: true to all three tool schemas to signal to LLMs that these are safe, non-destructive operations.
• Enhance fetch_product_page description to mention SSRF protection, soft-block detection, and Playwright fallback behavior so LLMs understand retry/fallback logic.