Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. read_github_repo and read_repo_file have acceptable descriptions (100+ chars) and input schemas with type info, but lack output schema documentation. create_project has a complex schema with nested objects (tasks, milestones) that lack internal field definitions. No tool has error handling guidance or recovery hints. Parameter descriptions are present but minimal (10-30 chars typical). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk profiles.

• Add explicit output schema documentation for each tool. For read_github_repo, document: {languages: [string], contributors: [object], readme: string, issues: [object], file_tree: [string], manifests: {[filename]: string}}.
• Expand create_project's tasks and milestones parameters with explicit object schemas: tasks: [{title: string, description: string, priority: enum(low|medium|high|urgent), status: enum(todo|in_progress|done)}].
• Add tool annotations: readOnlyHint=true for read_* tools, destructiveHint=true for create_project (since it persists data).
• Enhance parameter descriptions to 50-100 chars with constraints. E.g., 'Project name (2-100 chars, alphanumeric + spaces)' instead of 'Project name'.
• Add error handling guidance: 'If GitHub URL is invalid, try owner/repo format. If rate-limited, retry after 60 seconds. If repo is private, only public data is accessible.'

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

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