lazy-backlog registers 8 action-based tools with reasonable descriptions (avg ~120 chars), but suffers from critical naming and schema issues. Tool names lack action verbs (e.g., 'confluence', 'backlog', 'issues' instead of 'search_confluence', 'list_backlog_items', 'search_issues'). Input schemas are present and typed, but parameter descriptions are minimal and many lack guidance on valid ranges, formats, or dependencies. No output schemas documented. Error handling is generic. The action-enum pattern (action='index'|'search'|'get_page') conflates multiple concerns into single tools, violating single-responsibility principle. Tools like 'confluence' and 'backlog' each handle 3-5 distinct operations, forcing LLMs to reason about which action to invoke rather than selecting a tool by name.

• Rename tools to start with action verbs: 'search_confluence', 'list_backlog_items', 'create_issue', 'list_sprints', 'get_sprint_issues'. This enables LLMs to infer intent from the name alone.
• Split action-enum tools into separate tools. Instead of 'confluence' with action='index'|'search'|'get_page', create 'index_confluence_pages', 'search_confluence', 'get_confluence_page'. Each tool does one thing.
• Document output schemas for every tool. Specify which fields are returned, their types, and which are required for downstream tool calls (e.g., issue_id, issue_key, sprint_id).
• Add format/range constraints to parameter descriptions. E.g., 'maxDepth: integer, 1-50 (default 10)'; 'sprintId: Jira sprint ID (e.g., SPRINT-123)'; 'severity: one of Blocker|Critical|Major|Minor|Trivial, use Blocker for production outages'.
• Implement and document error handling with recovery guidance. E.g., 'Jira API returned 401 Unauthorized. Check that JIRA_API_TOKEN is set and has read:jira scope. Call configure(action=get) to verify credentials.'

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

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