Single tool with partial schema definition. Tool name 'MS_GRAPH_TOOL' lacks action verb (should be 'call_graph_api' or 'query_graph'). Description is adequate (97 chars, within 10-1024 range) but generic. Input schema present with Zod types but lacks critical parameter descriptions for 'path' and 'method', descriptions are minimal (10-15 chars). Output schema is documented in GraphResponse type but not exposed to LLM. No error handling guidance, no pagination support, no output field documentation. Tool performs write operations (POST/PUT/PATCH) but description does not warn of side effects. Parameters lack constraints (e.g., path format, method enum values are present but not described). No validation of GRAPH_API_TOKEN presence until runtime.

• Rename tool to 'call_graph_api' or 'query_graph_endpoint' to start with action verb and clarify intent.
• Expand parameter descriptions: 'path' should explain format (e.g., '/me', '/users/{id}', '/groups'), required vs optional segments, and URL encoding rules. Remove example values; use enum or pattern constraints instead.
• Add error classification to responses: return structured errors with 'category' (retryable|user_fixable|fatal), 'message', and 'suggestion' fields. E.g., 'category: retryable, suggestion: retry in 5 seconds'.
• Implement dry-run mode: add optional 'dryRun: boolean' parameter. When true, validate request but do not execute. Prevents accidental destructive operations.
• Document output schema in tool registration: add explicit 'outputSchema' field describing the GraphResponse structure (content array, isError flag, text/image/resource types) so LLM knows what to expect.