Artifacts demonstrates solid tool design with complete schemas, clear descriptions, and proper error handling. All 5 tools have explicit input schemas with typed parameters and descriptions. Tool names follow verb_noun convention (add_, update_, remove_, list_). Descriptions are concise (40-120 chars) and action-oriented. However, output schemas are not formally documented in the visible code, and some parameter descriptions lack constraint details (e.g., collection/project name format, length limits). Error handling is present but could be more prescriptive about recovery paths. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications in metadata.

• Document output schemas explicitly in tool definitions. For add_artifact, specify: returns {id, title, description, project, collection?, filename?, mediaType, type?, url, createdAt, updatedAt}. For list_artifacts, specify: returns {artifacts: [...], total: number}.
• Add tool annotations to schema. Mark remove_artifact with destructiveHint=true, add_artifact/update_artifact with idempotentHint=false (not idempotent on retry), list_* with readOnlyHint=true.
• Enhance parameter descriptions with constraints. E.g., 'project: Project name (1-100 chars, required, alphanumeric + hyphens)' and 'title: Short title (1-200 chars, required)'.
• Implement pagination for list_artifacts: add limit (1-100, default 20) and offset (default 0) parameters. Return {artifacts: [...], total: number, hasMore: boolean}.
• Improve error messages with recovery guidance. E.g., 'Invalid base64 in contentBase64: must be non-empty and canonical. Ensure the string is properly encoded (no line breaks), then retry.' for decodeBase64 errors.