Starlight Creator MCP has 16 tools with basic naming conventions (verb_noun pattern mostly followed), but critical gaps in schema visibility and parameter documentation. Tool descriptions are present but generic (avg ~60 chars, well below the 194-char baseline). No visible input schemas in provided source code, cannot verify parameter types, constraints, or output structures. Error handling and recovery guidance absent. Security considerations for irreversible operations (creator_publish) not evident. Composition is reasonable (tools are single-purpose), but lack of schema documentation and parameter descriptions severely limits LLM usability.

• Add explicit JSON Schema input definitions to all 16 tools. Include parameter types (string, number, boolean, array, object), required fields, enums for constrained values (e.g., model names, provider names), and min/max for numeric fields. Reference: pattern:constrained-input.
• Expand tool descriptions to 100 - 200 characters. For each tool, answer: (1) What does it do? (2) When should the LLM call it instead of similar tools? (3) What does it return? Example: 'creator_generate_image: Generate images via configured providers (OpenRouter, MuAPI, etc.). Use this to create visual assets from text prompts. Returns job_id for async polling and asset metadata on completion.'
• Document output schemas for all tools. Specify returned fields, types, and which fields are needed for downstream tool calls. E.g., creator_generate_image should return job_id (for creator_job_status), asset_id (for creator_assets), and provider_name (for creator_score).
• Add parameter descriptions to all tools. For generation tools, document: prompt (string, required), model (enum of available models), provider (enum or auto-select), quality/style parameters, and timeout. For approval tools, document confirmation_code format and retry behavior.
• Implement confirmation/dry-run for creator_publish. Add a 'dry_run' boolean parameter (default false) to preview publication without committing. For production publishes, require a confirmation_code from creator_publication_approve and validate it before executing. Document rollback procedures.