Server has 7 tools with basic descriptions and parameter schemas, but significant gaps in parameter documentation and output schema clarity. All tools are READ_ONLY and well-intentioned for incident response, but descriptions lack actionable context for LLM selection. Parameter descriptions are minimal (e.g., 'Maximum number of incidents to retrieve' for limit). No output schemas documented. Tool names follow verb_noun convention (get_*, correlate_*) which is good, but descriptions don't explain WHEN to use each tool vs. alternatives or what fields are returned.

• Document output schemas for all 7 tools. For each, specify: field names, types (string, number, array, object), and which fields are required. Example: 'Returns array of {incident_id: string, title: string, severity: enum(critical|high|medium|low), service_name: string, assigned_to: string}'. This enables LLMs to chain tools (e.g., extract service_name from incidents and pass to get_service_topology_tool).
• Expand parameter descriptions to include valid ranges, defaults, and side effects. E.g., 'limit: Maximum number of results to return (1 - 100, default 10). Larger limits increase response time; use pagination for large datasets.' This matches production baseline of 72 chars per param description.
• Add WHEN-to-use guidance to tool descriptions. E.g., 'Use get_dynatrace_problems_tool to find root causes of active issues. Use get_slo_status_tool to check if error budget is exhausted. Use get_service_topology_tool to understand blast radius before remediation.' This helps LLMs select the right tool for the user's intent.
• Clarify get_slo_status_tool behavior when slo_id is empty. Either: (a) document that it returns all SLOs, (b) make slo_id required, or (c) add a separate list_slos_tool. Current ambiguity invites misuse.
• Add error handling guidance to descriptions. E.g., 'If service_name is not found in get_service_topology_tool, the tool returns an error with available service names. Try search_services() to find the correct name.' This guides LLM recovery per pattern:recovery-guide.