Two tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema clarity, and error handling guidance. Tool names follow verb_noun convention (getApiOverview, getApiOperation), but descriptions lack context on when to use each tool and what structure is returned. Parameters have Zod type definitions but descriptions are minimal. No documented output schema. Error handling returns generic error text without recovery guidance. Missing parameter constraints (enums, ranges) and composition hints.

• Document output schema for both tools. Specify: does getApiOverview return a JSON object with fields like 'operations', 'paths', 'schemas'? What does getApiOperation return, a single operation object with 'parameters', 'responses', 'requestBody'? Include example structure.
• Add enum constraints to parameters. 'method' should be constrained to GET|POST|PUT|DELETE|PATCH|OPTIONS. 'id' description should clarify: 'Either an openapisearch.com API ID (e.g., "petstore") or a full URL to a raw OpenAPI JSON/YAML file (e.g., "https://example.com/openapi.json")'.
• Expand tool descriptions to 100-150 chars. getApiOverview: 'Fetch and parse an OpenAPI specification. Returns a summary of available operations, paths, and schemas. Call this first to explore an API before requesting specific operations.' getApiOperation: 'Retrieve detailed information about a single API operation. Provide either operationId (from overview) or path+method. Returns parameters, request/response schemas, and examples.'
• Add explicit parameter relationship documentation. For getApiOperation: 'Either operationId OR (path AND method) must be provided. If using path+method, method must be one of: GET, POST, PUT, DELETE, PATCH, OPTIONS.'
• Improve error messages with recovery guidance. Instead of 'SLOP API error: ...', return 'Failed to fetch OpenAPI spec from [id]. Verify the ID is valid (e.g., "petstore" from openapisearch.com) or the URL is accessible. Try a different API ID or URL.' For validation errors: 'Invalid parameters: path requires method. Provide both path and method, or use operationId instead.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry