Pocket Disasm provides 8 management tools with consistent naming (idb_* prefix) and clear descriptions (avg 95 chars). All tools have input schemas with typed parameters and descriptions. However, output schemas are not formally documented, responses are inferred from code inspection. Parameter descriptions are adequate but lack constraint details (ranges, enums, format specs). Error handling is present but generic; recovery guidance is minimal. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications in metadata.

• Document output schemas for all tools. Add a 'returns' field to each tool definition specifying the response structure (e.g., idb_open returns {name, state, pid, selected, error?}). Use JSON Schema format.
• Add tool annotations: mark idb_list, idb_health, idb_wait, idb_logs with readOnlyHint=true; mark idb_open, idb_select, idb_save with readOnlyHint=false; mark idb_close with destructiveHint=true.
• Enhance parameter descriptions with explicit constraints: 'timeout (seconds, 1 - 3600, default 300)', 'tail (lines, 1 - 300, default 100)'. Replace code-inferred limits with declarative specs.
• Improve error messages with recovery guidance. Instead of returning {error: str(error)}, return {error, code, retryable, suggestion}. E.g., 'Database session not found: xyz. Try idb_list to see available sessions.'
• Add a dry-run or confirmation step for idb_close. Accept an optional 'confirm' parameter or return a confirmation token that must be passed in a follow-up call to prevent accidental deletion.