Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. list_boards has 5 parameters with types and descriptions (good baseline), but get_board has only 1 parameter. Neither tool description explains what data is returned or when to use each tool vs. the other. No error handling guidance. Descriptions are adequate (60-80 chars) but lack context on prerequisites, return structure, or recovery paths. Parameter descriptions are present but generic ('Board ID (numeric, from list_boards)' is weak, doesn't explain what a board represents or why you'd fetch one). No tool annotations (readOnlyHint, idempotentHint) despite both being read-only. Output schemas are not documented in the tool definitions.

• Add explicit output schema documentation to each tool. Example for get_board: 'Returns: {boardId: number, name: string, type: "scrum"|"kanban", projects: [{key: string, name: string}], location: {projectKey: string}, settings: {...}}'.
• Expand tool descriptions to 100-150 chars explaining WHEN to use each tool and what data it reveals. Example: 'list_boards discovers available Jira boards filtered by type/name/project. Call this first to find a board ID, then use get_board for full details.'
• Add format/constraint details to parameter descriptions. Example: 'maxResults: Maximum results per page (1 - 1000, default 50). Larger values may timeout; use pagination for large result sets.'
• Document error scenarios and recovery paths. Example: 'If boardId is invalid, returns 404. Verify the ID via list_boards or check board permissions.'
• Add tool annotations (readOnlyHint: true, idempotentHint: true) to both tools so agents know they are safe to retry and do not modify state.