TinyTask MCP server demonstrates good definition quality with 31 well-named tools following verb_noun conventions. All tools have explicit descriptions (10-150 chars, within baseline). Input schemas are complete with type definitions and parameter descriptions. However, output schemas are not documented in the visible code, and several tools lack actionable error guidance. Tool names are clear and consistent, parameter constraints are well-defined (enums for status, optional flags for auto_promote), and descriptions explain WHAT tools do and WHEN to use them. The server shows evidence of thoughtful parameter design with created_by/updated_by tracking and relationship fields (parent_task_id, blocked_by_task_id). Missing output schema documentation and minimal error recovery guidance prevent a higher score.

• Document output schemas for all tools explicitly in source code or comments. Include field names, types, and whether IDs are stable references for downstream tool calls. Example: 'Returns {id: number, title: string, status: 'idle'|'working'|'complete', parent_task_id: number|null, ...}'.
• Add tool annotations to tool definitions. Mark destructive tools with destructiveHint, read-only tools with readOnlyHint, and idempotent operations with idempotentHint to signal tool safety to LLMs.
• Implement a two-phase confirmation flow for delete_task, delete_comment, delete_link, and clear_queue. First call returns {confirm_required: true, resource_id: ..., preview: '...'}; second call with confirm=true executes. This prevents accidental mass deletion.
• Enhance error messages with recovery guidance. Instead of 'Error adding comment: <raw error>', return structured errors like {error: 'TASK_NOT_FOUND', message: 'Task 42 not found. Try list_tasks() to find valid task IDs.', code: 404, retryable: false}.
• Add min/max constraints to parameter descriptions for numeric fields. Example: 'Priority level (-10 to 10, default: 0)' and 'Limit (1 - 100, default: 20)' instead of bare type declarations.
• Expand descriptions for destructive operations to emphasize irreversibility and encourage confirmation patterns. Example: 'Permanently delete a task and all its comments. This action cannot be undone. Archived tasks can be recovered; deleted tasks cannot. Use archive_task() for soft delete.'
• Add pagination metadata to list responses. Include total_count, offset, limit, and has_more so LLMs can reason about whether to fetch additional pages. Current list_tasks returns raw array without context.

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

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