Shiru exposes 8 tools with severe definition gaps. Most tools lack visible input schemas in the provided source code. Tool names use inconsistent patterns (healthCheck vs docs.publish vs onboarding.*). Descriptions are present but generic and lack actionable context. No parameter descriptions visible. No output schemas documented. Error handling and recovery guidance absent. Overall, this server falls well below production quality baselines.

• Expand tool names from wildcards to explicit, verb-noun pairs: 'onboarding.startFlow', 'onboarding.getStatus', 'organization.create', 'organization.update', 'user.create', 'user.update', 'user.delete', 'github.linkAccount', 'github.unlinkAccount'. Each tool should have one clear responsibility.
• Add 50 - 200 character descriptions to every tool explaining WHAT it does, WHEN to use it, and what it returns. Example: 'docs.publish: Fetch latest documentation from GitHub and publish to the live site. Use after updating docs in the repo. Returns publication status and timestamp.'
• Document input schemas for all tools with type, description, and constraints. Example for docs.publish: {"docsSiteId": {"type": "string", "description": "UUID of the documentation site (e.g., 550e8400-e29b-41d4-a716-446655440000)", "minLength": 36, "maxLength": 36}}
• Add output schemas showing response structure. Example: docs.publish returns {"status": "published|failed", "timestamp": "2024-01-15T10:30:00Z", "siteId": "string", "url": "string"}.
• Add error handling guidance. Example: 'If docsSiteId is invalid, returns 404 with message "Site not found. Call docs.getSiteSettings() to list available sites." Retry is safe.'