execute_luau

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

With no annotations, the description carries the full burden. It discloses the sandbox environment, lists blocked services, and notes restrictions on CoreGui/CorePackages. However, it doesn't explicitly describe potential mutability or destructiveness, which is inherent but should be stated for full transparency.

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 a single sentence, front-loaded with the purpose. Every phrase (PRO tag, execution capability, sandbox, restrictions) is necessary and concise.

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 (arbitrary code execution) and the lack of an output schema, the description is fairly complete. It covers the sandbox, blocked services, and return serialization. However, it could mention that this is for one-off execution or that it assumes developer privileges.

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 description coverage is 100%, so the baseline is 3. The description adds value by mentioning the sandbox and serialized returns, but it does not provide additional parameter-specific meaning beyond what is in the schema.

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 clearly states 'Execute arbitrary Luau code in Roblox Studio sandbox,' which is a specific verb-resource combination. The mention of blocked services and restricted access distinguishes it from sibling tools like batch_execute and specialized utilities.

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 implicit guidance through its list of blocked services and restrictions, but does not explicitly state when to use this tool versus alternatives like batch_execute. No comparison or exclusion criteria are given.

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