manage_studio

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the transparency burden. It discloses important behaviors: run_test injects Luau, plays, collects [ROBRIDGE_TEST] logs, stops, writes report, and auto-records a clip unless record=false. It also notes test_profile_get/set/reset have no public API and return manual_required, and experience_language_set is manual_required. This is substantial, though some actions like undo/redo/save_prompt lack detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and informative but delivered as a long run-on paragraph with a massive action list. It front-loads the purpose, but the list is hard to scan. Each piece of information earns its place, but the structure could be improved with line breaks or grouping for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (17 actions, 14 params, no output schema), the description covers a lot: run_test workflow, special manual_required cases, viewport clip behavior, and playtest guidance. It does not describe return formats for simple actions like get_mode or play_status, but the core behavioral expectations are well documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the schema already documents most parameters. The description adds meaning beyond the schema by explaining action-specific semantics: 'mode: play (F5) or run (F8)', 'toggle_ui_preview (StarterGui.ShowDevelopmentGui)', and run_test behavior including record defaults and timeout context. This complements the schema effectively.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Studio-level operations' and enumerates 17 distinct actions with specific verbs and targets (e.g., 'play_start', 'toggle_ui_preview', 'test_profile_get/set/reset'). This clearly differentiates the tool from sibling tools like manage_scripts or manage_camera. However, it is not a single specific action but a broad collection, which slightly reduces clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit workflow guidance: 'After adding a player-facing feature... playtest with run_test or play_start before reporting done' and 'Prefer run_test over manually sequencing play_start + logs + play_stop.' It also names an alternative for viewport clips ('manage_camera.record, or run_test'), satisfying the when-to-use vs alternatives criterion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.