ARTLIST — SINGLE PROPOSED TOOL VERSION FOR DEVELOPER REVIEW

This is a proposed tools/list snapshot, not a live-server export. It has 29 tools. All required annotation values are explicit booleans. It is the only tools-list JSON in this review ZIP. No tool name or input schema was changed. The live MCP server has not been edited or tested.

Changes
- Retained openWorldHint true on add_style_kit_item, upload_audio, upload_image, upload_video because their URL branches accept public external media sources.
- Proposed readOnlyHint false for upload_widget because its advertised purpose is to initiate an upload workflow. Verify the actual invocation: if it only displays a stateless panel and user upload is an independent action, true may instead be accurate.
- Removed preferential and overbroad selection language from generate_image, generate_video, generate_music, generate_3d_model, including unconditional instructions never to refuse edits.
- Scoped upload_widget follow-up instructions to existing authorization and preserved cost/consent gates.
- Rewrote create_style_kit to describe creating a kit and separate follow-up actions. Verify it creates an empty kit and does not itself fetch public URLs; revise the description/openWorldHint if the handler behaves differently.

Annotation reasoning
Read-only retrieval tools use readOnlyHint true, destructiveHint false, openWorldHint false because they read existing private-account records or bounded Artlist catalogs. This applies to get_balance, get_generation_cost, get_generation_status, get_model_config, get_recent_uploads, get_style_kit, get_track, list_generations, list_models, list_references, list_style_kits, list_voices, search_music. Verify polling and retrieval do not themselves mutate business state.

Generation tools, clone_voice, render_draft, upload tools, confirm_upload, style-kit writes, and upload_widget use readOnlyHint false because they create artifacts, queue jobs, store data, or initiate workflows. Bounded account/model operations retain openWorldHint false; the four public-URL ingestion tools use true.

Delete and update style-kit item tools use destructiveHint true because they delete or overwrite user data. Other writes retain false based on the described additive behavior, subject to verification below.

Checks that cannot be resolved from JSON alone
- Paid generation/clone/render tools: document credit debit/refund behavior and determine whether there is an irreversible transaction requiring destructiveHint true. Current false values are provisional; additive output and confirmation gates do not by themselves settle this.
- Verify image/video editing preserves original assets, render_draft preserves the original draft, and uploads/additions do not overwrite existing data.
- Verify clone_voice and model calls cannot target arbitrary destinations; a fixed service/provider alone does not make a tool open-world.
- Verify upload_widget invocation semantics and create_style_kit handler behavior as above.
- idempotentHint is omitted (optional). Add it only after verifying retries do not queue new jobs, charge again, or repeat writes.

Review cases
plugin.json contains five positive and three negative cases. get_balance now matches the actual supplied tool name. Supply a reference image for the image-to-video case. The negative voice-cloning test concerns unsupported YouTube-URL input, not all voice cloning: clone_voice supports stored audio. Run all cases with the dedicated review account.

Next step
Developers should review this proposal against the implementation, apply the final tool descriptions/annotations to the hosted MCP server, export its actual tools/list, and rescan it in Platform. Merely putting this file into a ZIP does not activate its annotations.

Official guidance
https://developers.openai.com/plugins/plugin-guidelines
https://developers.openai.com/plugins/reference
Current guidance requires explicit booleans and says annotation justifications are no longer required. The prior rejection requested explanations; these notes provide a behavioral explanation for review/clarification. No nonstandard justification property has been added to annotations.
