Critical structural deficiency: all 13 tools use a single 'action' string parameter with no enum constraint, forcing LLMs to guess valid action values from descriptions alone. No input schemas are visible in the provided source, only a generic action parameter is documented. Descriptions are present but generic (avg ~50 chars). No output schemas documented. Tools conflate multiple responsibilities (e.g., automad_pages handles get, create, update, delete, move, duplicate, publish, trash, history, breadcrumbs, publication_state, discard_draft, batch_update in one tool). This violates the single-responsibility principle and makes tool selection ambiguous for LLMs. Error handling and recovery guidance are absent. Security-sensitive tools (delete, publish, update) lack confirmation or dry-run patterns.

• Split each tool into separate verb_noun tools: automad_pages → get_page, create_page, update_page, delete_page, move_page, duplicate_page, publish_page, restore_page, etc. Each tool should do exactly one thing.
• Add enum constraints to all action parameters. Replace free-form 'action' string with explicit enum: {"type": "string", "enum": ["get", "create", "update", ...], "description": "The action to perform"}.
• Document output schemas for every tool. Specify return type, required fields, and field descriptions. Include IDs and references needed for downstream tool calls (e.g., page_id, media_id).
• Add parameter descriptions for all inputs beyond 'action'. If action='create', document required fields (title, content, etc.) and their types, formats, and constraints.
• Implement confirmation/dry-run for destructive operations. Add optional 'dry_run' boolean parameter to delete/publish/update tools. Return 'requires_confirmation' error with details before executing irreversible changes.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry