Critical failures across all dimensions. Tool descriptions are HTTP verb+path strings (e.g., 'GET /bookmarks/{namespace}'), under 20 chars, generic, and non-actionable for LLM tool selection. No output schemas documented. No error handling guidance. No parameter enums, ranges, or constraints. Tools like delete_bookmark_edit and delete_config expose destructive operations with zero confirmation or dry-run support. Parameter names are opaque (namespace, handle, key, extension) without type hints or resolution guidance. No evidence of idempotency, pagination, or composition patterns.

• Add 50-200 character descriptions to every tool explaining WHAT it does, WHEN to use it, and any prerequisites. Example: 'get_bookmark' → 'Retrieve a saved bookmark by namespace. Use this to load previously saved genealogy search filters or person records. Returns bookmark metadata and content.'
• Add non-empty descriptions to every parameter. Specify expected format, type, and valid values. Example: 'namespace' → 'The bookmark namespace (e.g., "person_search", "family_tree"). Used to organize bookmarks by feature area.'
• Document output schemas for all tools. Specify returned fields, types, and which fields can be passed to downstream tools. Example: get_person_dna_matches should return [{ person_id, match_name, confidence_score, ... }] so results can chain to other tools.
• Add confirmation/dry-run support to destructive tools (delete_bookmark_edit, delete_config). Implement a 'confirm' parameter or separate 'preview_delete' tool so agents can verify before executing irreversible operations.
• Replace opaque parameter names with type-suffixed names (e.g., 'namespace' → 'namespace_name', 'handle' → 'person_handle' or 'person_id'). Add enums for constrained values (e.g., extension: ['ged', 'csv', 'json']) and ranges for numeric params.

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

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