execute_luau

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

With no annotations, the description carries the full behavioral burden. It states the execution context and that output is returned, but says nothing about side effects, sandboxing, whether arbitrary code can mutate the scene, or required permissions — a serious gap for an arbitrary-code-execution tool.

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?

One compact sentence that front-loads the verb and resource and adds only the distinguishing context. No waste.

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?

No output schema, no annotations, and a single opaque code parameter mean the description must fill many gaps. It doesn't describe return shape, error behavior, or safety constraints, leaving an agent under-informed about invoking an arbitrary-code-execution tool.

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?

Single parameter with 100% schema description coverage ('Luau code to run'), so the baseline is 3. The description adds no format, version, or length constraints beyond what the schema already provides.

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?

States a specific verb (Executes), resource (Luau code), and scoping context (2021 Roblox Studio edit context) plus return behavior. An agent can distinguish it from siblings like run_playtest or start_playtest by the 'edit context' qualifier, though it doesn't explicitly name an alternative.

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 phrase 'in 2021 Roblox Studio edit context' implicitly tells the agent this is for edit-time scripting rather than playtesting, which is useful routing context. However, it names no explicit alternatives and gives no when-not-to-use guidance.

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