ShipCard MCP provides three read-only analytics tools with reasonable naming (verb_noun pattern: summary, costs, card) and consistent parameter schemas. All tools have descriptions (194 - 250 chars, within baseline 34 - 392 range) and input schemas with typed parameters. However, output schemas are not documented in the visible code, parameter descriptions lack actionable constraints (e.g., date format examples, enum values for 'layout', 'style', 'theme'), and error handling guidance is absent. The 'card' tool has 6 parameters but no documentation of mutual exclusivity or defaults. No tool declares permissions or risk levels explicitly in descriptions.

• Document output schemas for all three tools. Example: 'summary returns {sessions: number, totalTokens: number, models: string[], totalCost: number, toolCalls: number}'.
• Convert 'layout', 'style', 'theme' parameters to enums with explicit allowed values. Example: layout: enum ['classic', 'compact', 'hero']. Add 'hide' array enum: ['sessions', 'toolCalls', 'models', 'projects', 'cost'].
• Add actionable error descriptions to tool docs. Example: 'If projectsDir does not exist, returns error: "Directory not found at {path}. Ensure ~/.claude/projects exists or pass a valid path."'
• Document parameter interdependencies in 'card' tool. Example: 'heroStat is only valid with layout=hero. If layout is classic or compact, heroStat is ignored.'
• Add result limits and pagination guidance. Example: 'summary returns up to 100 sessions. For larger datasets, use 'since' and 'until' to filter by date range.'