Server has 4 tools with complete Zod schemas and descriptions. Naming follows verb_noun convention (ping, crawl-start, crawl-status, crawl-cancel). Descriptions are present and adequate (50-150 chars). However, parameter descriptions lack actionable constraints (e.g., 'limit' has no min/max bounds despite API docs mentioning max 100000). Error handling returns generic text responses without recovery guidance. Output schemas are not documented, callers cannot predict response structure. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. crawl-start has 14 parameters, some with complex interdependencies (e.g., 'source' enum affects URL discovery) that are underdocumented.

• Add min/max constraints to numeric parameters: limit (1 - 100000), depth (1 - 10), maxAge (0 - 31536000), cursor (0+). Use Zod .min().max() and document in descriptions.
• Document output schemas as JSDoc comments or inline descriptions. E.g., 'Returns {jobId: string, status: string, createdAt: ISO8601}' for crawl-start.
• Enhance error responses with structured objects: {error: string, code: string, retryable: boolean, suggestion?: string}. E.g., 'Invalid limit: 150000 exceeds max 100000. Retry with limit ≤ 100000.'
• Add tool annotations via registerTool metadata: crawl-start with destructiveHint=true, crawl-cancel with destructiveHint=true, crawl-status with readOnlyHint=true.
• Clarify parameter relationships in descriptions. E.g., 'source: URL discovery method. Use "sitemaps" for sitemap.xml-based crawls; "links" for link-following; "all" for both. Ignored if includePatterns is set.'

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

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