PortZero MCP server has 7 well-named tools with clear action verbs (list_, get_, replay_, restart_). All tools have descriptions (avg 95 chars, within 10-1024 range). Input schemas are present and properly typed with JSON Schema. However, parameter descriptions are sparse or missing in several tools (e.g., get_recent_requests has 6 params but only 4 have descriptions; replay_request's 'headers' param lacks detail on merge semantics). Output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance or actionable error messages visible. Tool composition is sound (single responsibility), but missing pagination guidance for list_apps and get_recent_requests despite potentially large result sets.

• Document output schemas for all 7 tools. Include field names, types, and descriptions. Example: list_apps should return {apps: [{name: string, status: 'running'|'stopped', port: number, url: string}], total: number}.
• Add descriptions to all parameters in get_recent_requests. Clarify that 'status_range' accepts '2xx', '3xx', '4xx', '5xx' and that 'limit' defaults to 20 with a max of 100.
• Expand replay_request 'headers' description: 'Headers to override or add (merged with original request headers; original values are preserved unless explicitly overridden).'
• Add pagination support to list_apps and get_recent_requests. Include 'offset' and 'limit' parameters, and return a 'total' count so LLMs know if more results exist.
• Add error handling guidance to tool descriptions. Example for restart_app: 'Returns error if app not found (suggest list_apps to discover available apps) or if restart fails (retryable).' Use pattern:recovery-guide.